One thing I would like some feedback on however: the current default system debugger is like CLs debugger. I stand by this, but the debugger hook is bound to nil by default, meaning the system debugger is invoked.
I would like this library to be usable in library code as well, not only applications. The way to allow this to be done is to ensure that conditions don’t introduce any new concepts when signaled without handlers bound. The only change this requires to farolero as it stands is to make there be a default debugger hook which will throw the condition as an exception.
So my question is, given a default behavior of throwing the conditions as exceptions as the default debugger (with the option to bind the existing debugger if you want it), would you consider using farolero in library code, as well as applications?