-
Notifications
You must be signed in to change notification settings - Fork 358
Migrate to JSpecify annotations for nullability constraints #1980
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
Hi, @mp911de! Could I work on this issue or maybe a part of it? From what I understand, the task is about replacing @nullable and @nonnull annotations with JSpecify annotations, e.g., ensuring that the necessary imports are in place where they are currently used. Is there anything else I should know before I start working on this? Thanks! |
Hey @ivamly. There's quite a bit more attached to this task. JSpecify annotations relate to the type level while Spring's I highly suggest waiting until common infrastructure and dependency management in the build infrastructure is in place (see spring-projects/spring-data-commons#3170). If you give this topic another month or two, then you should have everything in place to start with the task on the module level. |
Thanks! I’ll wait for that. |
Kotlin reacts to JSpecify with increased nullability requirements. See #1980
Kotlin reacts to JSpecify with increased nullability requirements. See #1980
Kotlin reacts to JSpecify with increased nullability requirements. See #1980
Kotlin reacts to JSpecify with increased nullability requirements. See #1980
Kotlin reacts to JSpecify with increased nullability requirements. See #1980
Kotlin reacts to JSpecify with increased nullability requirements. See #1980
Kotlin reacts to JSpecify with increased nullability requirements. See #1980
Kotlin reacts to JSpecify with increased nullability requirements. See #1980
Kotlin reacts to JSpecify with increased nullability requirements. See #1980
Kotlin reacts to JSpecify with increased nullability requirements. See #1980
No description provided.
The text was updated successfully, but these errors were encountered: