Matt Parsons
Matt Parsons
That does work, thank you! But now I am finding that I'm actually a bit confused about the intention of `callerAttributes`. ```haskell inSpan :: (MonadUnliftIO m, HasCallStack) => Tracer ->...
I do think there's value in providing a `class (Monad m) => MonadSpan m where inSpan :: (span arguments) -> m a -> m a`, even if that ends up...
I'm in favor of removing it or replacing with a re-export of `Data.Functor.void`.
Would we want a stack of `ThreadId`? Consider async exceptions: thrown in one thread, received in another, and potentially bubbling up to `main` via `async` and `link`.
Looks great to me, thanks for putting this together!
+1, anything that reduces `length` on lists is a win
I helped a small amount with the proposal and am in favor. While there are some design quibbles re exactly what information gets retained and how to handle duplication, they...
FWIW, I'm totally fine with PVP exclusions, provided the modules are named in a manner that suggests that and documented as excluded. While I *do* prefer to see packages extracted...