requireNotNull function throws an
IllegalArgumentException instead of the more precise
> requireNotNull(null) java.lang.IllegalArgumentException: Required value was null.
Josh Bloch suggests in “Effective Java” to use the most precise Exception available, what is a
NullPointerException in this case (and exactly this case in the book).
Why does Kotlin treat it differently? Shouldn’t it be changed?