`Null type safety` warnings occur in method references that take primitive values as arguments

[mazeneko]

When such code is written, a warning occurs.
But I expected no warning here.

Is this behavior reasonable?

package example;

import java.math.BigInteger;
import java.util.List;
import java.util.Optional;

public class App {
    public static void main(String[] args) {
        List.of(1, 2, 3)
                .stream()
                .map(BigInteger::valueOf)
                .forEach(System.out::println);

        Optional.of(1)
                .map(Math::incrementExact)
                .ifPresent(System.out::println);
    }
}

Environment

• Operating System: Windows10
• JDK version: JDK17
• Visual Studio Code version: 1.71.2
• Java extension version: 1.11.0

[CsCherrYY]

looks like related to #2731

[jkaye2012]

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).

[fbricon]

Null-analysis improved at some point, the warnings no longer appear on those methods: