• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Generics

 
Jon Camilleri
Ranch Hand
Posts: 664
Chrome Eclipse IDE
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
"One of the notable features of Java generics is the erasure of generic types in the virtual
machine. Perhaps surprisingly, the erased classes still retain some faint memory of their
generic origin
"
Core Java Vol I (8th Ed) P. 641

Somehow this reminds me of weak references, is this correct?
Can we read this information somehow?

Related links?
1. Weak references
2. Understanding weak references
 
Jesper de Jong
Java Cowboy
Saloon Keeper
Posts: 15205
36
Android IntelliJ IDE Java Scala Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
No, this does not at all have anything to do with weak references.

Is there some more context in the book? (I don't have the book so I can't look it up).
 
Stephan van Hulst
Bartender
Posts: 5334
48
  • Likes 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I assume it has to do with the fact that when you compile the code, the bytecode still knows that it is generic, so if you write new code that interacts with this compiled class, it will be able to perform type safety checks, as opposed to compiled code that used raw types. All the erasure actually takes place right before run time. This is when all generic information is discarded.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic