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
Resource Leak processor throws an exception when @MustCall is annotated on a Type Variable #4815
Comments
Thank you for reporting the crash! We appreciate it. I have committed the test case as The crash does not occur when running the Must Call Checker with |
#4821 resolves the crash. A false positive error is still issued by the checker (which isn't ideal), but I think that's a separate issue (I don't think the Called Methods Checker handles type variables very precisely). |
Should we file a follow-up issue to fix the false positive, or keep this issue open for that problem as well? |
I think a follow up issue would be better. I'll wait until this one is closed, though. |
Closed in favor of #4837, which describes only the false positive. The crash (which this issue represents) has been fixed. |
Commands
./checker-framework-3.16.0/checker/bin/javac -processor resourceleak MustCallBug.java
Inputs
Outputs
Expectation
Checker Framework should be able to handle this example and not throw an exception.
The text was updated successfully, but these errors were encountered: