Open wildwind123 opened 12 months ago
Please take time to explain what you expected: a meaningful title, a summary of the issue. Readers can't spend time deciphering your code.
Please take time to explain what you expected: a meaningful title, a summary of the issue. Readers can't spend time deciphering your code.
done
@wildwind123 thanks for reporting the issue! We have implemented support for analyzing anonymous functions. However, currently it is hidden under a feature flag. You can add <nilaway anonymous function enable>
to the file docstring to enable this feature, which will report the expected error in the go-routine code snippet.
We are conducting performance and correctness evaluations internally for the anonymous function feature before moving it to main NilAway. I'm keeping this issue open to track the work.
this code from https://github.com/uber-go/nilaway/blob/main/README.md
after run command
catch possible nil.
but if i wrap "print(*foo()) " in go-routine this does not detect
after run command
does not catch possible nil, should catch, like from first example