[code-reflection] RFR: Conflicting code reflection fields for method overrides [v2]

Adam Sotona asotona at openjdk.org
Fri Jun 28 16:20:42 UTC 2024


On Fri, 28 Jun 2024 16:03:33 GMT, Adam Sotona <asotona at openjdk.org> wrote:

>> Could we encode an instance of `MethodRef` in the field name like we do with the invoke operation's descriptor? (I believe there are less restrictions in the names of synthetic fields than ones that can be denoted in source.) That might be easier to manage on the compile time and run time sides.
>
> Technically to create fields  `<method name>+<signature>+$op` still looks like a quick workaround.
> Can we introduce a custom method attribute or annotation?

> Could we encode an instance of `MethodRef` in the field name...

Maybe I don't know all the javac tricks, but I understand the `MethodRef` instance is composed a bit later in the process. Here we try to reconstruct the composition of it (or at least the method parameters).

-------------

PR Review Comment: https://git.openjdk.org/babylon/pull/162#discussion_r1658968156


More information about the babylon-dev mailing list