You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
Yeah, that's been a thorn in my side for a while. I was working on a fix at one point, but that got stuck and ended up on the low priority pile for awhile.
Have you decided what designs are acceptable, though? It seems that an interface change in ThreadBracket is inevitable in a new version of broadcast-extra that uses resourcet-1.3.
There is a breaking change in resourcet-1.3 related to
Data.Acquire.ReleaseType
whereReleaseException
is replaced byReleaseExceptionWith
.This affects
BroadcastChan.Conduit.Internal
, which usesReleaseException
, including for constructing aBroadcastChan.Extra.ThreadBracket
whereincleanupForkError
does not get the exception to use forReleaseExceptionWith
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 evenBroadcastChan.Extra.ThreadBracket
needs to change.The text was updated successfully, but these errors were encountered: