Chris Povirk

Sadly, it's pretty much as you say: We all want for `@NullMarked` to be the default, but there are a zillion lines of unannotated Java code for which that's not...

There was some discussion relatively recently on the ancient https://github.com/jspecify/jspecify/issues/8. It seems likely to be another thing that individual tools can choose to support but that JSpecify would not. In...

For some writing we've done on the idea of a "`@DefaultNullable`" annotation, see these two FAQ entries: - [Why does being null-marked require us to explicitly mark our nullable types,...

In an ideal world, it would be possible to run nullness checking on null-unmarked code. (Our reference checker supports this, though it has its own limitations :)) Such a checker...

(I'll also say that this is another case in which nullness will feel a lot less burdensome if it becomes possible to write "`Foo?`" instead of "`@Nullable Foo`." Hopefully [someday](https://openjdk.org/jeps/8303099)....)

> (btw if Kevin sees this I can't signup for project Loom's mailinglist for some reason but it would be great if they do not add PolyNull `orElse` to `ScopedValue`...