merijn / broadcast-chan Goto Github PK

I have broadcaast-chan installed, but yet it's not "sending" it
Setup: Encountered missing dependencies:
broadcast-chan >=0.2.0.2

I see back on March 6th the upper bound of base was bumped.
On hackage it's still saying it requires base <4.14, though - so I can't build it on GHC 8.10
Could we get a new release published to hackage?

For my use case, it would be quite useful if the broadcast channel would always retain the most recent value that was written to it (even in the case where there are 0 readers).

I realize that it may not make sense to implement this in this library, but I thought I might mention it just in case it does.

e.g. ['BroadcastChan' 'In':]: gets rendered as BroadcastChan Direction:

https://hackage.haskell.org/package/broadcast-chan-0.2.1.1/docs/BroadcastChan.html#v:newBChanListener

Source:

Rendered:

I'm planning to use this library but want to be really sure of what it's doing and its intended purpose. Would it be possible to explain at a conceptual level how the code is working and how it fixes the problem with using dupChan for creating broadcast channels? (especially for the case where we may have zero readers). What's the kind of overhead/performance-hit that one can expect from using broadcast-chan?

Is there any technical reason why the readBChan and writeBChan functions from the BroadcastChan.Throw module are in IO and not some MonadIO m => m? Since the equivalent functions from the BroadcastChan module are in MonadIO m => m.

I need to get broadcast-chan into stackage because it is a dependency of taffybar. Would you like to put it under your name or mine.

There is a breaking change in resourcet-1.3 related to Data.Acquire.ReleaseType where ReleaseException is replaced by ReleaseExceptionWith.

This affects BroadcastChan.Conduit.Internal, which uses ReleaseException, including for constructing a BroadcastChan.Extra.ThreadBracket wherein cleanupForkError does not get the exception to use for ReleaseExceptionWith value construction. Thus, the changes necessary for using resourcet-1.3 are non-trivial and require code changes and not just .cabal changes, and perhaps even BroadcastChan.Extra.ThreadBracket needs to change.