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.

Sign up for GitHub

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

Jump to bottom

Properly handle @NullUnmarked generic types #872

Open
msridhar opened this issue Nov 29, 2023 · 1 comment
Open

Properly handle @NullUnmarked generic types #872

msridhar opened this issue Nov 29, 2023 · 1 comment
Labels
jspecify Related to support for jspecify standard (see jspecify.dev)

Comments

@msridhar
Copy link
Collaborator

Right now, we report an error for code like java.util.function.Function<@Nullable String,String> f = ... since we think Function has a non-null upper bound. But, since we currently treat Function as @NullUnmarked we shouldn't be doing this check in the first place. We need to tweak some of our JSpecify checking to detect when relevant code is @NullUnmarked` and bail out.
@msridhar msridhar added the jspecify Related to support for jspecify standard (see jspecify.dev) label Nov 29, 2023
@msridhar
Copy link
Collaborator Author

FYI @akulk022

This was referenced Apr 14, 2024
Open
Draft
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
jspecify Related to support for jspecify standard (see jspecify.dev)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@msridhar