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

document pipes vs comm #3334

Closed
jesse99 opened this issue Sep 1, 2012 · 2 comments
Closed

document pipes vs comm #3334

jesse99 opened this issue Sep 1, 2012 · 2 comments
Milestone

Comments

@jesse99
Copy link
Contributor

jesse99 commented Sep 1, 2012

The relation between pipes and channels/ports should be documented somewhere (maybe just a doc comment). Is comm now deprecated and pipes are the replacement? Or is comm now acting as a simpler wrapper on top of pipes?

@brson
Copy link
Contributor

brson commented Sep 3, 2012

The current situation is definitely transitional, but unfortunately it's going to be like this for a while. The intention is that pipes implements the low level pipe infrastructure, then comm be replaced with pipe-based equivalents, but it's not clear yet how to proceed.

I would like to write some documentation on concurrency in rust in general. There are quite a number of tools available now but they are mostly still in the realm of experimental and underdocumented.

@brson
Copy link
Contributor

brson commented Oct 5, 2012

There is a discussion of this issue in the task tutorial now.

@brson brson closed this as completed Oct 5, 2012
bors pushed a commit to rust-lang-ci/rust that referenced this issue May 15, 2021
fix Inconsistency between  loop  and while
RalfJung pushed a commit to RalfJung/rust that referenced this issue Mar 3, 2024
remove a wrong bitwise negation

This is a silly mistake I introduced in rust-lang/miri@a1233a7.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants