<flatwhatson>please let me know if you notice something that could be handled better, error parsing is very ad-hoc as guile is not always super consistent, the checker is basically a collection of regexes to parse out useful info from the various forms
<antipode>the 'handler' needs to be run in the right context for backtraces (when using #:unwind? #t) or for the outer parametrisations (when using #:unwind? #false), but fiddling with which handler is run seems weird to me.
<antipode>Wasn't there something about Guile's implementation of 'guard' being incorrect because it runs the clauses in the wrong dynamic environment, but a proper implementation would be inefficient (due to it requiring continuations?)?
***nikken_ is now known as nikken
***wklew_ is now known as wklew
***arrdem_ is now known as arrdem
***fluffyballoon_ is now known as fluffyballoon
***ane__ is now known as ane
***\f_ is now known as \f
***unmatched-paren_ is now known as unmatched-paren