On Friday, 31 August 2018 at 21:40:50 UTC, tide wrote:
The asserts being there still cause slow downs in things that would otherwise not be slow. Like how D does assert checks for indices.
After the bug is fixed and the app is debugged, there's no need to keep those assertions. The release switch will do the job. Anyway, what's that got to do with the topic of this thread?
That's assuming an assert catches every error. Not all bugs are going to be caught by an assert.
not really, at least that's not what I meant. (well, in theory one could write enough assertions to detect any error, but... nvm, I agree with you). What I meant were apps misbehaving because of obviously ignored errors.
I don't think I've ever had a game hung up in a black screen and not be able to close it.
Lucky one :)
