-
Notifications
You must be signed in to change notification settings - Fork 727
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
UnnecessaryOptionalGet gives false-positive #2101
Comments
copybara-service bot
pushed a commit
that referenced
this issue
Jan 14, 2021
…entical don't assume that a particular receiver symbol already corresponds to the same `Optional`, which results in false positives when the same method is called on two different instances. Fixes #2101 PiperOrigin-RevId: 351873201
copybara-service bot
pushed a commit
that referenced
this issue
Jan 14, 2021
…entical don't assume that a particular receiver symbol already corresponds to the same `Optional`, which results in false positives when the same method is called on two different instances. Fixes #2101 PiperOrigin-RevId: 351873201
copybara-service bot
pushed a commit
that referenced
this issue
Jan 14, 2021
…entical don't assume that a particular receiver symbol already corresponds to the same `Optional`, which results in false positives when the same method is called on two different instances. Fixes #2101 PiperOrigin-RevId: 351873201
Thanks @cushon that was quick! |
stevie400
pushed a commit
to HubSpot/error-prone
that referenced
this issue
Jan 15, 2021
…entical don't assume that a particular receiver symbol already corresponds to the same `Optional`, which results in false positives when the same method is called on two different instances. Fixes google#2101 PiperOrigin-RevId: 351898477
This was referenced Mar 13, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description of the problem / feature request:
UnnecessaryOptionalGet
gives a false-positive when two, different instances of the same type holding Optional are used.Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
Gives false-positive:
which is not correct obviously.
What version of Error Prone are you using?
2.5.0
Have you found anything relevant by searching the web?
Nope :)
The text was updated successfully, but these errors were encountered: