Evan Relf

@tsani No worries! Unfortunately I'm not familiar enough with why the change was made, why it's problematic for cases like this, or why the solution works. But I think a...

 Is there any way to highlight based on the backticks? And maybe you could check from the type annotation above, where it...

I prefer to keep a minimal dependency footprint. The `unliftio` package handles most of the standard-library-ish combinators like `bracket`, `catch`, `async`, etc. And for libraries like `network-simple`, it's possible to...

`drama` depends on `unliftio-core` (contains just the `MonadUnliftIO` type class), not `unliftio` (contains lots of standard library stuff).

You're right, and I agree 🙂 I would just change `receive` to the new behavior, no extra version.

I agree, that would be a useful addition. I can't think of a reason the library should forbid equating `Address`es, off the top of my head.

You make a good point! 🙂 It would be more pure (and Erlang/Elixir-y) to recurse with the new state, rather than using a mutable cell. I think your pure `receive'`...

Y'all just calm down and be patient, it'll be released when it's ready and no sooner.

If I understand correctly, I believe the team working on the Zed text editor implemented something similar to this in their GPUI crate. They describe the concept in this blog...

Some other ideas to consider: - Follow the `withFile` style instead of `openFile`: ```diff -handleFrom :: OutputOpt -> IO Handle +withHandleFrom :: OutputOpt -> (Handle -> IO a) -> IO...