I love this project and particularly its documentation. But: > Design Goals > - Simplicity (...) is the amount of information it takes to describe a system.

I love this project and particularly its documentation. But: > Design Goals > - Simplicity (...) is the amount of information it takes to describe a system. > (...) > > Anti-Features > - There are no exceptions > > (Error handling etc. omitted for clarity.) At first sight, error handling is going to be laborious in this language. I wonder what's the state of the art in PL theory regarding error handling in a context without automatic resource management. Anything better than manual bubbling up of errors up the chain of callers until one takes responsibility?