Hello, Class-File API has a convenient Signature model API, which can replace the Generic Tree internal API in the current core reflection implementation. The old internal Tree API + visitor pattern was bloated with a lot of unnecessary classes, which can be removed with the new CF API.
A working implementation with all tier 1 tests passing is available at https://github.com/openjdk/jdk/compare/master...liachmodded:jdk:feature/new-generic-info?expand=1 . In my implementation: - reflectiveObjects (classes directly implementing ParameterizedType, etc.) remain; they are exported, and their implementation is sufficient as-is. - all other old generic classes are removed - few existing usages of old generic code moved to BytecodeDescriptor, use sites converted to throw GenericSignatureFormatError (preexisting behavior) instead of IllegalArgumentException - Just 5 new classes are added to replaced all removed old classes. Given the size of this patch, I decide to start a discussion on the mailing lists on this proposal. Is there any shortcomings with this patch, or is there anything that I should be cautious of for this patch? Best regards, Chen Liang
