4 ms·
this is a case of the programmer calling his function inside an assert macro, which disappears in the preprocessing step when you compile with -D NDEBUG
by erubin 10y ago
this is a case of the programmer calling his function inside an assert macro, which disappears in the preprocessing step when you compile with -D NDEBUG
- Chilinot 10y agoNo, he/she checked the return value of the function inside an assert macro. But since Visual Studio no-opped the assert in release mode, the compiler found no use in keeping the returned value of the recursive fibonacci code and thus removed the function call altogether.