Recognize contractual non-nullness of standard library functions

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

Nell’issue non sono indicati file sorgente né test. Inizia esaminando come l’estensione delega l’analisi della nullità a Eclipse JDT e confronta le annotazioni compatibili con JDT di LastNPE con il supporto EAA richiesto; il lavoro è completo quando i metodi della libreria standard come Integer::toString non producono più avvisi di cast non verificato quando vengono assegnati a campi @Nonnull.