There seems to be some debate over refactoring to use java generics in my current team. I have a question, what are the current industry standards in terms of reorganizing old Java code to take advantage of some of these features? Of course, by industry standards, I mean best practices. A link to a book or website with the lists you have indicated will be marked as an answer, since this is the least subjective way to resolve this issue.
The documents from this MIT study group can provide you with some useful suggestions:
, , - " " " ", . , , .
, , - , , ?
, , , . . , generics, , , , . / .
- , , . , , , , . ? , , .
java - . . , , , .
EDIT. erasure , .
? "". , . , IntelliJ "Generify" - , , .
... , .
" " , -, .
. , , "" ... ? . . , (Hibernate, Spring) - .. , , - , .
, , - .
, .
, , , , , , .
:
- , , , - Java . !
, :
MyClass<T>
- , 10 000 Java , .