On Tue, 23 Sep 2025 14:02:53 GMT, Chen Liang <li...@openjdk.org> wrote:
>> Some type parameter declaration signatures in class and method generic >> signatures, such as `<T:R:>`, are valid per JVMS but are not accepted by >> either the ClassFile or the legacy core reflection parser. (Javac doesn't >> generate these because it always generates an Object upper bound) They can >> be constructed by the ClassFile API models. So it makes sense to support >> their parsing as supported by JVMS and our API model. > > Chen Liang has updated the pull request with a new target base due to a merge > or a rebase. The pull request now contains eight commits: > > - Merge branch 'master' of https://github.com/openjdk/jdk into > fix/cf-typevar-parse > - 8368331: ClassFile Signature parsing fails for type parameter with no > supertype > - More fixes > - Fix bad docs and add more to clarify class type sig > - Merge branch 'master' of https://github.com/openjdk/jdk into > fix/cf-classtypesig-factory-classdesc > - Fix links > - More bugs > - 8368050: Validation missing in ClassFile signature factories This makes it possible to denote `T extends (ref or primitive)` in a way which differentiates it from `T extends ref Object`. ------------- PR Comment: https://git.openjdk.org/jdk/pull/27439#issuecomment-3324973272
