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

Consider allowing the default Map constructor also to have null-checks performed #1

Open
tvinke opened this issue Jun 13, 2017 · 0 comments
Assignees

Comments

@tvinke
Copy link
Owner

tvinke commented Jun 13, 2017

Have the default Map constructor also check for null values.

@tvinke.bulletproof.transform.NonNull
class Person {
    String name
}
new Person() // should also throws IllegalArgumentException: "Name can not be null"
@tvinke tvinke self-assigned this Jun 13, 2017
@tvinke tvinke added this to the v0.2 milestone Jun 13, 2017
@tvinke tvinke removed this from the v0.2 milestone Aug 2, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant