Gracefully handle critical CLA failures
I checked the issues mentioned in #88 (closed) - we have two options to handle these
cases; a) continue working but without the broken functionality active
or b) stop the program. The ASSERT(0)
will do b) in debug builds and
a) in release builds, which is IMO the right way to do it. This commit
just adds a return
to prevent additional behavior to bb triggered in a
release build.
Fixes: #88 (closed)
Depends on: !83 (merged)
Edited by Felix Walter