Is there any way to improve the quality of stacktraces for exceptions returned by a series of d/chain or d/catchs? I seem to lose all context of any functions run as part of the d/chain or d/catchs

I don't see the same issue if operating on a realized error-deferred

@callum it's in the nature of composed chains of async operations - each time an op is parked any stack context is effectively erased... i have an idea for using a Deferred<Writer> monad-transformer and a defn-wrapping macro for achieving async call-tracing, but i haven't done anything with it yet