Details
-
Improvement
-
Status: Closed
-
Trivial
-
Resolution: Fixed
-
None
-
None
-
None
Description
Following the discussion on the "dev" ML, it appears that it would be fine to not check for null references within CM. The JVM will do it anyway so that it is redundant and not necessary most of the time (i.e. when usage is valid). When it happens, the problem is obvious enough that the standard NullPointerException fully describes it, without the need for additional specific and localized detailed messages.
Hence we could remove all explicit checks for null. Or when early failure is preferred, make the check and throw NullPointerException (without a message argument).
Since failed checks are currently reported with an IllegalArgumentException, the change is not backward-compatible.