-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Fix Java record problems (#19578) and (#19386) #19583
Conversation
It seems that #19578 is still failing. |
should link this to #18639 |
I started taking a look at this. I don't think the issue is in the parser - the type parameter looks good within the |
@yilinwei I haven't started anything yet so please feel free |
This fixes a whole host of subtle issues. - The type parameter was not stamped correctly on the constructor causing the original error - The parsed record was not stamped with `JavaDefined`, which meant the duplicate constructors in the case of overrides were not removed.
Turned out you were right, problem was in the parser @bishabosha, and that the parsed tree didn't trigger the correct branches within the This should be all good to go, if it doesn't cause any other regressions. |
We change the proxy method to take in a single argument. This also exposed a second issue where the overriden methods were not invalidated correctly in the `Namer`.
@nicolasstucki @bishabosha is there anything I can do to help move this along? |
I've just been busy, sorry, free tomorrow |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good, and I tried with some other variants, thanks for seeing this through!
@Kordyjan Will this be backported to 3.3.x? |
I too am anxiously waiting for this to be back-ported to 3.3.x as well. |
) Backports #19583 to the LTS branch. PR submitted by the release tooling. [skip ci]
This is a dependency of #19577 and should be reviewed and merged first.
fixes #18639
fixes #19386
fixes #19578