Comment 1 Ed Willink 2013-08-21 06:59:55 EDT

From playing around with adding @NonNull myself it looks the following are easy and safe:

In generated code:

all List-returning getXXX methods return @NonNull

static constants such as eINSTANCE are @NonNull

all createXXX methods return @NonNull

EcoreSwitch cases have an @NonNull argument

In support code

all URI create methods return @NonNull and many other methods too.

Moving on to @NonNull/@Nullable for arguments requires more careful consideration, but if the declarations are accurate it should only break code that has requested to be broken by enabling the analysis.

Comment 2 Ed Merks 2018-02-12 06:32:44 EST

No, this is too much noise of questionable value.