[7.0] Use JSpecify annotations #1010
Merged
+36
−29
Conversation
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
Member
Author
|
Scrapping setting up NullAway for now, so I can get to work on more pressing matters. |
Jonathing
changed the title
Jonathing
force-pushed
the
feat/jonathing/7.0/jspecify
branch
from
424ec56 to
6eaee56
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR replaces the usage of JetBrains annotations with JSpecify. JSpecify is one of the newer nullable annotation standards that most people have begun to agree on, including Gradle and Mojang.
This is still a work-in-progress. Part of this PR is getting NullAway and Errorprone working for enhanced static analysis on build of ForgeGradle 7.