Nevermind, I found this section in the docs: > ...

# getting-started

[waylonbrown]

Nevermind, I found this section in the docs:

An explicit call to throw NullPointerException()

Usage of the !! operator that is described below

External Java code has caused it

There's some data inconsistency with regard to initialization (an uninitialized this available in a constructor is used somewhere)