Open mazeneko opened 2 years ago
looks like related to https://github.com/redhat-developer/vscode-java/issues/2731
This issue significantly hampers the usefulness of null analysis, at least for me. While I do agree that the warning is often technically valid, in reality these methods end up being used in many places all over most code bases, resulting in a significant amount of warnings generated from non-user code (as we have no way to alter these method contracts without e.g. wrapping every unboxing operation ourselves).
When such code is written, a warning occurs. But I expected no warning here.
Is this behavior reasonable?
Environment