Stephan Herrmann

In my experience words like "unknown" will easily entail questions like: "why doesn't the tool know? Can't it figure it out?" etc. At Eclipse we had similar fights with the...

As mentioned in #62 the ambiguity whether "unspecified" includes the parametric case, can be reduced by consistently naming that latter case, either as "parametric", or - as I prefer -...

Thinking of naming the checking modes: does the "lenient" mode exactly mean to be tolerant towards legacy code? Does this make it a "migration" mode? I'd like to signal that...

It's a pity that `Joiner` is not generic. Otherwise it would be a nice example for parametric nullness: `on()` would return a `Joiner`, whereas `skipNulls()` would return `Jointer`. The argument...

I very much like the idea of `@UnderMigration`. I briefly thought about the correspondence to enhanced deprecation, but - their `since` attribute is restricted to JDK versions, so not usable...

For clarification: how does the discussion in this issue relate to code ownership: - is it about code owned by the same party where just some internal API have been...

Thanks for bringing this up! In addition to `@SuppressWarnings` Eclipse also has a few precedents where line comments control reporting of warnings, like `//$NON-NLS-1$`, `//$FALL-THROUGH$` etc. If the group considers...

> But it sounds like your position is that Map.get is clearly @Nullable, as are the Android cases, but you're willing to live with the Android team's decision to apply...

I'm late for sure, but .. ... if this is still relevant, I'd be interested in the following: * the `.classpath` files of projects involved, and * any additional compiler...

Found two JDT bugs: * Normally using a modern ecj, methods `java.util.Objects.requireNonNull(..)` should be understood in terms of nullness _even without any external annotations_, but this is broken when `--release`...