> All try/catch based systems always develop an "uncaught exception" at some
> point in their lifetime, because an underlying library added a new exception
> of some kind.
Isn't this what the effects system is for? You can stick `{.raises: [].}` on
your main proc and be confident that no pesky new exceptions slipped in.
I'm mostly working with embedded platforms where I don't need or want
exceptions, but on desktop I have no problem with them, they seem like the
lest-terrible tool for the job, a happy medium between being _forced_ to check
things vs. having to _remember_ to check things.
