Define an Error Handling Strategy #33
Description
Current assertion system sucks and is minimalist.
It's enough so far but will quickly find it's limits.
Also it is not clear what to do in the backend when invalid values are passed by arguments. Should it crash? Should it throw an exception? Which exception? Undefined behaviour maybe?
It have to be either defined or configurable using the assertion macro. (which might require work on utilcpp).
Deciding what to do in the default frontend too will be important. The current behaviour is to either crash or report a problem into the log.