[Pre-RFC?] NonNaN type

This is not a really good comparison. Out of bounds errors are not only logic errors but they're memory unsafe. Thats a whole other ballgame. Also i'm pretty sure that the performance impact is a lot smaller than checking each and every floating point operation since we work with iterators most of the time and if not, the CPU is probably waiting for the indexed memory anyway.

A better (but still not 100% apt) comparison would be integers. Overflow is checked in debug builds, but wrap around in release builds. This can lead to logic (but not memory access) errors, but is the right trade off since the performance hit would be to large for the gain.

2 Likes