Right now, we report an error for code like java.util.function.Function<@Nullable String,String> f = ... since we think Function has a non-null upper bound. But, since we currently treat Function as @NullUnmarked we shouldn't be doing this check in the first place. We need to tweak some of our JSpecify checking to detect when relevant code is@NullUnmarked` and bail out.
Right now, we report an error for code like
java.util.function.Function<@Nullable String,String> f = ...
since we thinkFunction
has a non-null upper bound. But, since we currently treatFunction
as@NullUnmarked we shouldn't be doing this check in the first place. We need to tweak some of our JSpecify checking to detect when relevant code is
@NullUnmarked` and bail out.