Weird error messages with `NaN`s

[Ayc0]

In the following image, we can see that typanion understands NaN as null in error message:

This can lead to problematic error report, but also to weird cases like:

t.isNullable(t.isString())(NaN, {errors});
// logs "Expected a string (got null)"

but null should have been understood as isNullable was used