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

Remove OptionalEmptinessHandler method for propagating access paths to lambdas #953

Open
msridhar opened this issue Apr 28, 2024 · 0 comments · May be fixed by #954
Open

Remove OptionalEmptinessHandler method for propagating access paths to lambdas #953

msridhar opened this issue Apr 28, 2024 · 0 comments · May be fixed by #954

Comments

@msridhar
Copy link
Collaborator 

          We are in fact missing coverage!  It turns out that #678 made the pseudo-field simulating contents of an `Optional` final, which means we already (safely) propagate nullability facts about that pseudo-field into lambdas, which means we no longer need this handler method!  I'll go ahead and delete this method in a separate PR.  Nice to have the test coverage exposed!

Originally posted by @msridhar in #952 (comment)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Delete OptionalEmptinessHandler method that is no longer needed msridhar/NullAway
1 participant
@msridhar