Conversation
Chrimle
force-pushed
the
jspecify
branch
2 times, most recently
from
June 25, 2026 21:28
aa8a270 to
58e1c6e
Compare
Owner
Author
|
useJspecify appears to still not be production-ready... No support for enums, and barely coverage of classes... |
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 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.
Checklist
Each item in the list MUST either be checked ([x]) or crossed off (
~).<version>inpom.xmlTo update the project version, run the following command locally:
mvn versions:set -DnewVersion=versionanddate-releasedinCITATION.cffmvn clean installgenerated-sources-filesREADME.md&index.md) have been updated