-
Notifications
You must be signed in to change notification settings - Fork 72
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
Handle iterators introduced in Go 1.23 #287
Comments
NilAway is panicking on code that ranges over iterators. This PR adds initial handling for such that we assume the results from the iterators are always nonnil, without panicking. See #287
Is there someone still working on this issue? Currently, nilaway can't work with programs written with Go 1.23. |
Hey @spacewander , could you share the logs for "nilaway can't work with programs written with Go 1.23"? We had a PR landed to at least not panicking for iterators, and we assume the results from the iterators are always non-nil (such that it can lead to false negatives), but it should be working fine for other patterns. |
Glad to hear that there is an ongoing PR addresses this issue! |
It is actually already merged #288, could you verify that you're on the latest version? Also, when you say "won't work anymore", could you clarify it a bit? Does it show some errors (panics), or does it simply stop reporting previously-reported diagnostics? 🤔 |
I got some messages about iter when running nilaway with a project configured with Go 1.23:
Not sure if it is related. |
Go 1.23 introduced iterators, which NilAway does not support yet. This issue tracks such support.
Initially, we should at least assume these are deeply nonnil without panicking.
The text was updated successfully, but these errors were encountered: