Skip to content
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

Add nullness annotations #511

Open
NiccoMlt opened this issue Nov 6, 2024 · 1 comment · May be fixed by #514
Open

Add nullness annotations #511

NiccoMlt opened this issue Nov 6, 2024 · 1 comment · May be fixed by #514
Assignees

Comments

@NiccoMlt
Copy link
Contributor

NiccoMlt commented Nov 6, 2024

Java experience can be greatly improved with annotations that help track nulls, i.e. @Nullable and @NonNull.

In Java history, there are many efforts to do so, like:

JSpecify is being created by a group led by Google (with EISOP Team, Google, JetBrains, Meta, Microsoft, Oracle, PMD Team, Sonar, Square, Uber, VMware) with the aim to create a tool-independent nullness annotation standard which is modern enough to replace JSR-305.

It recently received the first stable release with stable APIs to be used, and it seems that it is getting adoption.

@NiccoMlt
Copy link
Contributor Author

NiccoMlt commented Nov 6, 2024

I think an acceptable choice would be to adopt the annotations first with not actual implementations to leverage IDE help during development without introducing anything into the build.

When the adoption in our codebase will be complete, we could start thinking about what implementation introduce into the build to actually check the code.

@dmercuriali @hamadodene what do you think about this?

@NiccoMlt NiccoMlt self-assigned this Nov 7, 2024
NiccoMlt added a commit that referenced this issue Nov 13, 2024
track #511 for news
@NiccoMlt NiccoMlt linked a pull request Nov 13, 2024 that will close this issue
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 a pull request may close this issue.

1 participant