Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[DPP-65] AsyncChan should behave more like a... well, channel. #118

Open
qnikst opened this issue Jun 17, 2015 · 0 comments
Open

[DPP-65] AsyncChan should behave more like a... well, channel. #118

qnikst opened this issue Jun 17, 2015 · 0 comments

Comments

@qnikst
Copy link
Contributor

qnikst commented Jun 17, 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.

@qnikst 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant