On Fri, 5 Dec 2025 23:36:22 GMT, Chen Liang <[email protected]> wrote:
> Core reflection has its own type conversion behavior that is somewhat poorly
> specified; it is scattered around a few places, and its boxing and unboxing
> deviates from that of Java language assignment contexts. In addition, core
> reflection has a somewhat erroneous access check system. We can improve the
> overview of java.lang.reflect to address these shortcomings and recommend
> users to use java.lang.invoke for better functionality in these areas.
src/java.base/share/classes/java/lang/reflect/package-info.java line 53:
> 51: * member inherited by another reference type from A with equivalent
> reflective
> 52: * objects, with A as the {@linkplain Member#getDeclaringClass()
> declaring class
> 53: * or interface}. Therefore, access checks of such a reflected object
> assumes
Suggestion:
* or interface}. Therefore, access checks of such a reflected object assume
-------------
PR Review Comment: https://git.openjdk.org/jdk/pull/28685#discussion_r2679667347
