The idea behind removal of the runtime checks is as a performance optimization done on a debugged program. It's like turning on or off array bounds checking. Many leave asserts and array bounds checking on even in released code to ensure memory safety.

At a minimum, turning it off and on will illuminate just what the checks are costing you.

It's at the option of the programmer.

Reply via email to