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
[Imported from JIRA. Reported by Tim Watson [Administrator] @hyperthunk) as DPP-65 on 2013-01-26 01:40:23]
Currently AsyncChan is a one shot deal, unlike its cousin AsyncSTM. This is probably wrong however, in as much as the suffix 'Chan' makes it sound like a channel, whilst it behaves more like a synchronised cell or an MVar.
I think it would be cool if AsyncChan actually behaved like a channel, allowing multiple values to be streamed back to the caller but without them knowing any details about the implementation (i.e., we continue to hide the typed channel inside).
It'd also be nice if these could be composed, though perhaps that's another issue by itself.
The text was updated successfully, but these errors were encountered:
qnikst
changed the title
AsyncChan should behave more like a... well, channel.
[DPP-65] AsyncChan should behave more like a... well, channel.
Jun 18, 2015
[Imported from JIRA. Reported by Tim Watson [Administrator] @hyperthunk) as DPP-65 on 2013-01-26 01:40:23]
Currently AsyncChan is a one shot deal, unlike its cousin AsyncSTM. This is probably wrong however, in as much as the suffix 'Chan' makes it sound like a channel, whilst it behaves more like a synchronised cell or an
MVar
.I think it would be cool if
AsyncChan
actually behaved like a channel, allowing multiple values to be streamed back to the caller but without them knowing any details about the implementation (i.e., we continue to hide the typed channel inside).It'd also be nice if these could be composed, though perhaps that's another issue by itself.
The text was updated successfully, but these errors were encountered: