Description Srikanth Sankaran 2011-12-07 03:24:14 EST

3.8 M4 candidates.

In the following program both the assignment and return statement
are violating the null contracts in exactly the same way, but the
diagnostics are different. One is a warning and the other an error.
This is inconsistent:

import org.eclipse.jdt.annotation.NonNull;
import org.eclipse.jdt.annotation.NonNullByDefault;
import org.eclipse.jdt.annotation.Nullable;


public class X {
	@NonNull
	public Object foo(Object x, int y) {
		@NonNull Object local;
		while (true) {
			if (y == 4) {
				local = x;  // error
				return x;   // only a warning.
			}
			x = null;
		}
	}
}