If you’re like me, you use a lot of jasserts while developing your project. However, when building release versions, all of those jasserts disappear.
if we’re doing something like:
auto f = someFunctionThatModifiesInternalState(); jassert( f < someValue );
The compiler is going to throw a warning that
f is an unused variable during a release build.
it would be rad if
jassert() internally used
ignoreUnused(); to eat up those variables so they aren’t considered ‘unused’ anymore. I’m not sure how you could make that happen, since jassert expects an expression, and not individual variables, but it would be handy nonetheless. somethin’ to think about…