Skip to content

[deprecated] Add JSpecify annotations#2963

Closed
MukjepScarlet wants to merge 0 commit intogoogle:mainfrom
MukjepScarlet:jspecify
Closed

[deprecated] Add JSpecify annotations#2963
MukjepScarlet wants to merge 0 commit intogoogle:mainfrom
MukjepScarlet:jspecify

Conversation

@MukjepScarlet
Copy link
Copy Markdown
Contributor

Purpose

Description

closes #2952

Checklist

  • New code follows the Google Java Style Guide
    This is automatically checked by mvn verify, but can also be checked on its own using mvn spotless:check.
    Style violations can be fixed using mvn spotless:apply; this can be done in a separate commit to verify that it did not cause undesired changes.
  • If necessary, new public API validates arguments, for example rejects null
  • New public API has Javadoc
    • Javadoc uses @since $next-version$
      ($next-version$ is a special placeholder which is automatically replaced during release)
  • If necessary, new unit tests have been added
    • Assertions in unit tests use Truth, see existing tests
    • No JUnit 3 features are used (such as extending class TestCase)
    • If this pull request fixes a bug, a new test was added for a situation which failed previously and is now fixed
  • mvn clean verify javadoc:jar passes without errors

@MukjepScarlet MukjepScarlet deleted the jspecify branch March 23, 2026 14:36
@MukjepScarlet MukjepScarlet restored the jspecify branch March 23, 2026 14:36
@MukjepScarlet MukjepScarlet changed the title Add JSpecify annotations [deprecated] Add JSpecify annotations Mar 23, 2026
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.

Apply jspecify nullability annotations for better Java & Kotlin experience

1 participant