This repository was archived by the owner on Jun 3, 2024. It is now read-only.
Correct ExtendedForgeRegistryEntry's bytecode interface and correct the generics on ForgeRegistryEntry#141
Merged
coderbot16 merged 1 commit intomasterfrom Jul 25, 2020
Conversation
coderbot16
approved these changes
Jul 25, 2020
Member
coderbot16
left a comment
There was a problem hiding this comment.
Seems simple enough, but be prepared to make a second PR if this breaks 🙃
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Should've been part of #131, but didn't notice in time. It turns out that ForgeRegistryEntry has the generic
<V extends IForgeRegistryEntry<V>>, not just<V>and we need to mimic the bytecode that would produce.