This message was deleted.

Umm, that would be very shocking to me if we're doing that. Are you sure you're using the same version of the Kotlin stdlib in both your tests?

In one of the test case first operand was becoming 0, thus causing 0/0=NaN. False alarm, sorry. I thought 0/0 also throws an exception but it doesn’t.