Issues: jspecify/jspecify
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Document the nullness of special APIs on enum and annotation types
#509
opened Apr 29, 2024 by
cpovirk
Document on how to add the jspecify dependency: Maven and Gradle
#503
opened Mar 29, 2024 by
sdavids
Figure out and document whether module-level
@NullMarked
helps users who don't declare a module
#496
opened Mar 15, 2024 by
cpovirk
Document how to declare that your JPMS module uses JSpecify
#495
opened Mar 14, 2024 by
xenoterracide
Give advice in docs about the "findViewById problem"
documentation
For issues related to user-facing documentation
nullness
For issues specific to nullness analysis.
Document that we ignore For issues related to user-facing documentation
implies
For issues with the `@Implies` annotation (name TBD).
@Inherited
documentation
Not possible to annotation a return enum @Nullable from a method
discussion
Something that did or will resolve itself without any actual change needed
nullness
For issues specific to nullness analysis.
#492
opened Mar 12, 2024 by
alexandrenavarro
Take the Javadoc warning down a notch
documentation
For issues related to user-facing documentation
nullness
For issues specific to nullness analysis.
Consider annotating Question of how a particular library should be annotated; could potentially affect design or docs
nullness
For issues specific to nullness analysis.
InvocationTargetException
, ExecutionException
, and CompletionException
causes as non-nullable
library-use-case
@ValueClass
, to prepare a class for Valhalla transition (also immediately useful)
design
Move module-info back to the main root?
dev
development tasks, build issues...
#484
opened Feb 22, 2024 by
cpovirk
How to annotate Question of how a particular library should be annotated; could potentially affect design or docs
nullness
For issues specific to nullness analysis.
Collection.toArray(T[])
library-use-case
No access to Java-concepts glossary
documentation
For issues related to user-facing documentation
#460
opened Jan 25, 2024 by
kashike
Documentation for code authors
documentation
For issues related to user-facing documentation
nullness
For issues specific to nullness analysis.
Document intended pre-1.0 releases, including release candidates
documentation
For issues related to user-facing documentation
User Guide: Type-use annotation syntax for full qualified names
documentation
For issues related to user-facing documentation
nullness
For issues specific to nullness analysis.
#453
opened Jan 12, 2024 by
bjmi
What about lazy initialization/setters
discussion
Something that did or will resolve itself without any actual change needed
nullness
For issues specific to nullness analysis.
#431
opened Dec 15, 2023 by
danthe1st
Standard set of declaration-annotation equivalents to An issue that is resolved by making a decision, about whether and how something should work.
needs-decision-post-1.0
Issues needing a finalized decision that they are post 1.0
new-feature
Adding something entirely new for users, not improving what's there
nullness
For issues specific to nullness analysis.
@Nullable
and @NonNull
design
Javadoc "Why?" links don't appear to include the section header
documentation
For issues related to user-facing documentation
nullness
For issues specific to nullness analysis.
#408
opened Aug 14, 2023 by
cpovirk
AtomicReference.compareAndSet: Question of how a particular library should be annotated; could potentially affect design or docs
nullness
For issues specific to nullness analysis.
(V?, V%)
or (V%, V%)
?
library-use-case
Previous Next
ProTip!
Adding no:label will show everything without a label.