Skip to content
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

Merged
merged 47 commits into from
Jun 2, 2024
Merged

Merge/0.8.6 #141

merged 47 commits into from
Jun 2, 2024

Conversation

LlamaLad7
Copy link
Collaborator

@LlamaLad7 LlamaLad7 commented May 19, 2024

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.

Mumfrey and others added 30 commits December 1, 2021 20:50
Fixes remapping of synthetic members in resolvable classes.

(cherry picked from commit c33a48b)
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.
@LlamaLad7 LlamaLad7 marked this pull request as draft May 20, 2024 00:45
@LlamaLad7
Copy link
Collaborator Author

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.
@LlamaLad7
Copy link
Collaborator Author

Pulled said changes in early here.

@LlamaLad7 LlamaLad7 marked this pull request as ready for review June 1, 2024 17:26
@LlamaLad7
Copy link
Collaborator Author

The fix to NEW descriptor filtering is potentially breaking so I will gate it.

@LlamaLad7 LlamaLad7 marked this pull request as draft June 1, 2024 17:37
@LlamaLad7 LlamaLad7 marked this pull request as ready for review June 1, 2024 17:59
@LlamaLad7 LlamaLad7 requested a review from Chocohead June 1, 2024 18:00
Copy link
Member

@modmuss50 modmuss50 left a 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.

@modmuss50 modmuss50 merged commit 02f8479 into FabricMC:main Jun 2, 2024
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants