-
Notifications
You must be signed in to change notification settings - Fork 294
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
Investigate warnings from JSpecify mode on caffeine #1002
Comments
Couple of quick observations here.
This is a false positive due to #674. I should re-prioritize that one and try to fix it soon (though it's a bit messy). Generally we've tried to specifically look for
To me this looks like a real issue. With JSpecify semantics, I would expect the |
It is expected that this would show up only when JSpecify mode is enabled or it just dumb luck?
I am planning on mirroring Guava and migrate when they have. That's mostly because the previous annotation discussions are a lot of bike shedding that I don't enjoy (maven dependency scope, stylistic semantics, etc). Pushing those who like to argue towards Guava helps me close the issues and say that I'll follow whatever best practices the broader community chooses. Hopefully they make the transition soon with 1.0 released (congrats!) so I'll do a fast follow.
That seems reasonable to me. |
I think our current hacks make things work outside JSpecify mode. I'm not exactly sure why they don't work in JSpecify mode; you're right that might be a separate issue from #674. |
Originally posted by @ben-manes in #996 (comment)
The text was updated successfully, but these errors were encountered: