Type erasure in Java alludes to the cycle by which conventional type information is taken out (or "eradicated") during aggregation. Generics were introduced in Java to give more grounded type-checking at assemble time and to empower engineers to make reusable, type-safe code.
At the point when you proclaim a nonexclusive type, for example, List, the compiler guarantees type security by checking that main String items can be added to or recovered from the list. Be that as it may, at runtime, this information about generics is not accessible because of type erasure. https://www.sevenmentor.com/java-training-classes-in-pune.php
This is the way type erasure works:
Accumulation: During arrangement, Java's generics are checked for type security. This means that if you attempt to add an object of some unacceptable type to a conventional assortment, the compiler will make a mistake.
Type Erasure: After accumulation, the compiler eliminates the nonexclusive type information. This is finished to maintain similarity with more established variants of Java that don't uphold generics. For instance, List is eradicated to just List, and List is additionally deleted to List.
Bytecode Age: The compiler creates bytecode with the nonexclusive type information eliminated. Thus, at runtime, the JVM (Java Virtual Machine) doesn't have information about the conventional types utilized in the program.
Due to type erasure, the JVM treats all instances of a conventional type with various type boundaries as though they were a similar type. This can sometimes lead to startling ways of behaving or runtime mistakes if legitimate precautionary measures are not taken. To relieve this, Java utilizes methods, for example, type casting and type inference to guarantee type wellbeing even after type erasure.
Type erasure considers in reverse similarity with pre-conventional Java code yet can once in a while prompt restrictions or intricacies in working with generics, particularly in situations where runtime type information is essential.