A modern programming language that makes developers happier.

kotlinlang

<https://github.com/FasterXML/jackson-module-kotlin/issues/192>

What you want is not possible. Even if Kotlin does not emit runtime type assertions, as far as Kotlin reflection is concerned, the type is still e.g. `String`, which _cannot_ be null.

If you want `null` to end up in a property _at all_, the property _must_ have a nullable type. Hacking around with disabling the assertions is a terrible idea. You will receive random `NullPointerExceptions` in places. The assertions have a reason...

no, the validation will be done by other tool, like `@NotNull` annotation

why is it not possible? the library just should check if kotlin throw any exceptions

The library checks the types reported by Kotlin reflection.

Validation and type-system are different things. Just because the values are validated, they still can be null as far as the compiler is concerned.

&gt;The library checks the types reported by Kotlin reflection.
Why? Why just not to pass them to constructor and check the exception?

&gt;Validation and type-system are different things
in this case they are the same, both do validation

but kotlin intrisics fail on first argument, `@NotNull` can return all arguments that violate contract