Oddbean new post about | logout
 @986ebc02 i think because an assertion error will cause death and a stack trace in debug rigs, whereas return won't.

(although in a release build it won't early return, so :blobcatwaitwhat:) 
 @ @986ebc02 usually there is assert( 0 ); return; in these cases. So it returns in release builds and asserts in debug builds.

But I would rather not use assert at all. Different program behavior in debug and release builds is evil. 
 @0xa1baa1baa1baa1ba @986ebc02 its usually game devs who are stuck with the cursed RelWithDebugInfo build :neocat_nervous: 
 @ @986ebc02 RelWithDebugInfo is the one configuration that makes sense for release. You just strip out debug info before shipping binaries and store debug info for each version somewhere.

Sure, debug info in optimized build lose some data, but not everything. 
 @0xa1baa1baa1baa1ba @ there are many cases without return in mesa. And it's code paths that will hang gpu 
 @986ebc02 @ good job mesa