[lworld] Dropping jdk.incubator.mvt and MVT change in MethodHandle and reflection (original) (raw)
John Rose john.r.rose at oracle.com
Tue Feb 27 17:31:02 UTC 2018
- Previous message (by thread): [lworld] Dropping jdk.incubator.mvt and MVT change in MethodHandle and reflection
- Next message (by thread): [lworld] Dropping jdk.incubator.mvt and MVT change in MethodHandle and reflection
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Feb 27, 2018, at 9:20 AM, Karen Kinnear <karen.kinnear at oracle.com> wrote:
2) java/lang/invoke/MethodHandles.java There should be no constructor for value types. I believe Srikanth is ensuring that in javac, and the jvm will be ensuring that at runtime. So maybe that means that no constructor will be found. Would it make sense for findConstructor to check for isValue and throw NoSuchMethodException directly? Or does that fall out of the ResolveOrFail call?
Careful with this point: Value types have no meaningful but they do have a meaning constructor at source level. This means the findConstructor for a value type really just finds the factory.
— John
- Previous message (by thread): [lworld] Dropping jdk.incubator.mvt and MVT change in MethodHandle and reflection
- Next message (by thread): [lworld] Dropping jdk.incubator.mvt and MVT change in MethodHandle and reflection
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]