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

Extend null-safety to field level [SPR-15720] #20276

Closed
spring-projects-issues opened this issue Jun 29, 2017 · 0 comments
Closed

Extend null-safety to field level [SPR-15720] #20276

spring-projects-issues opened this issue Jun 29, 2017 · 0 comments
Assignees
Labels
type: task A general task
Milestone

Comments

@spring-projects-issues
Copy link
Collaborator

spring-projects-issues commented Jun 29, 2017

Juergen Hoeller opened SPR-15720 and commented

After the measures in #20099, we have consistent @Nullable declarations at the method parameter and return type level already. It turns out that @Nullable at the field level is an essential companion, avoiding mismatches between methods and the fields that they access.

Also, Eclipse only supports "full" nullability through annotations: that is, it doesn't differentiate between parameter level and field level. Extending our @NonNullApi / @Nullable semantics to the field level makes it easier to set those up for Eclipse as well.


Affects: 5.0 RC2

Issue Links:

Referenced from: commits 46eba3d, 9fc4fb1, 00f4c36, c292a89, 301e2ea, cc74a28, 57f961e

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: task A general task
Projects
None yet
Development

No branches or pull requests

2 participants