Repository navigation
Recognize contractual non-nullness of standard library functions #2731
Description
The nullness analyzer does not recognize that certain standard library functions will, contractually, never return null. A common example would be Integer::toString.
These methods will generate unchecked cast warnings if assigned to a @Nonnull field.
As I understand, the plugin relies on Eclipse JDT for nullness analysis. I have come across LastNPE, which publishes JDT-compatible external null annotation files for many common libraries.
Would it be possible to include these annotations by default? Alternatively, if this is not desirable, could EAA files be supported by the plugin?
Environment
- Operating System: Windows 10 Enterprise
- JDK version: openjdk 11.0.12 2021-07-20
- Visual Studio Code version: 1.71.2
- Java extension version: v1.11.0
Activity
t-kozak commentedon Oct 10, 2023
When I asked AI bots about how to enable EAA support for Java extension in VSCode, it recommended setting the following setting:
"java.jdt.ls.vmargs": "-Dorg.eclipse.jdt.core.compiler.annotation.externalAnnotationsPath=<path_to_externalAnnotations_directory>"Unfortunately, it does not seem to worry, yet another hallucination. Would it be possible for maintainers here to confirm or deny whether we can configure the EAAs?