Adam Gent

I agree with others and I don't think it should be a requirement of any checker that is turned on by default to require use of Guava (or I guess...

It is my number one `@SuppressWarnings` (other than some Eclipse issues with null). I use parameterized testing with enums so I have lots of enums that take lists.

I think the best compromise if Error Prone is going to be adamant about the list having "Immutable" in the name is perhaps this is only applied if the enum...

This is very similar to `Optional` `orElse` but Optional `orElse` is far worse because passing `null` is extremely common especially in a null annotation world. Regardless like @cpovirk I have...

See https://github.com/lastnpe/eclipse-null-eea-augments/issues/141 Where I believe someone wanted it to be `@Nullable` but with `getProperty` which is another analog to `getOrDefault`.

> Checker Framework: @SuppressWarnings("nullness") > Eclipse: @SuppressWarnings("null") @kevinb9n @cpovirk @msridhar I must admit that @stechio has some good points here that there is no standard. I myself have like three...

I know have said this probably too many times but again it is best to think of JSpecify and the annotations as types especially similar to generics. That is TYPE_USE...

> analogously to the way it automatically infers the same suppression through an explicit asset statement (please, look beyond my literal words and get the concept): > — BTW, assertions...

@ceki I'm shocked this was a patch change and not a minor change. What is the point of `initialize` then. https://github.com/jstachio/rainbowgum/issues/210

Like @TWiStErRob pointed out with their Kotlin implementation I was safely checking for null as I use JSpecify/Checker. @ceki I now initialize the MDCAdapter and MarkerFactory in the service provider...