In the past we had doAssert() for checks always enabled, and assert() which was disabled in release built.
But with Nim 1.0 we generally avoid -d:danger, so assert() is generally enabled.
For example in
https://github.com/StefanSalewski/RTree/blob/master/src/rtree.nim
I have many asserts, some look really stupid. So one may not like to have them enabled in release builds. So manually comment them out? But remove comment sign again manually when we work on that package again? Or totally remove the stupid asserts? OK, I think I could indeed remove a few. But still, I think that something like debugAssert() which is disabled for -d:release would be nice. Or do we already have that? Have not seen it.
assercho is like assert(conditionBool, errorString) + echo(Nim_Code) + printf(C_Code).
It only works when not defined(release) and not defined(danger). 🙂