-
-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support Java 16 language features #40
Comments
It's probably a consequence of the JDT being old in the published build - will update and publish a new Mercury version soon. |
0277125 may well present a fix, unsure though. |
Looks like we'll have to wait until JDT 3.26 - https://github.com/eclipse/eclipse.jdt.core/commit/fd6db01a1ee874ef9fe027d48fc549331ceea29a#diff-23943f685010f4e86bb88902ca769cd7ad6df4c88119e62dfbd50fcc1ec34474R21 |
Tested with Mercury 0.1.0 and manually bumping JDT to 3.27.0, records still don't remap properly/at all. References to records get remapped properly, however records themselves are not remapped. Top level records have the .java file renamed and nothing else, inner records fail to remap and seem to cause Mercury to give up on remapping that java file. |
Ran into this when using Loom's Since I control the mod source, the solution was to use intellij's "convert record to class" intention on all the records, run the Gradle task, then convert them all back |
The issue occurred when trying to
migrateMappings
in a Fabric project (running Loom 0.8, 1.16.5 mod). May be an issue with some Java 16 feature, that class uses at leastvar
. Assumed it's a Mercury issue since it's present in many positions in the stacktrace.Stacktrace
Class where it fails
Also (not sure if this is an issue with Mercury or not), after removing that class and running
migrateMappings
again, classes which declared records as nested classes got a failingimport record;
in their list of imports, andvar
was replaced with the actual type.The text was updated successfully, but these errors were encountered: