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
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?
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.
Activity
brson commentedon 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 commentedon Oct 5, 2012
There is a discussion of this issue in the task tutorial now.
Merge pull request rust-lang#3334 from rchaser53/issue-3227
Auto merge of rust-lang#3334 - RalfJung:nullfix, r=RalfJung