-
Notifications
You must be signed in to change notification settings - Fork 42
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
Merge/0.8.6 #141
Merge/0.8.6 #141
Conversation
Fixes remapping of synthetic members in resolvable classes. (cherry picked from commit c33a48b)
… Mirror. (cherry picked from commit e5d9db4)
(cherry picked from commit c902985)
(cherry picked from commit 0fb3116)
Extending an already-compiled mixin no longer results in an error, and extending (a mixin that targets) your target class does result in an error. (cherry picked from commit 7f7dbc1)
We no longer use mirror. The generics are irrelevant in the first place because Mixin does not check them at runtime. (cherry picked from commit ccfb5ee)
…onment rather than on the Package specification version, since that version is unavailable in two scenarios: 1) ML loaded as a JPMS module and 2) ML added to the classpath using a folder rather than JAR-file.
I've asked Mumfrey to make one other change to support MixinExtras, will wait for his response before doing it here. |
…nd un-deprecate it. The only reason MixinExtras uses this method is to match Redirect's behaviour, so I would like it to be kept in line with that. Additionally, there is nothing wrong with not checking the desc as long as you've definitely found the right `NEW` insn, which the injection point handles itself.
Pulled said changes in early here. |
The fix to |
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.
Basically impossible for me to review (due to the size and my lack of knowlage :D ).
The compat fix looks good, im happy to merge and do a release of this so the loader side of things can be looked at.
Also pulls in 1 commit from the upcoming 0.8.7 since Mumfrey accidentally broke MixinExtras.
A couple of our changes were reverted to ease the merge of their upstream equivalents.
Generally I tried to reduce the diff where possible.
Works fine in the latest AOF7.
Requires changes in loader to support the new compatibility version.