Skip to content

document pipes vs comm #3334

Closed
Closed
@jesse99

Description

@jesse99
Contributor

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?

Activity

brson

brson commented on Sep 3, 2012

@brson
Contributor

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

brson commented on Oct 5, 2012

@brson
Contributor

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

added a commit that references this issue on May 15, 2021

Merge pull request rust-lang#3334 from rchaser53/issue-3227

e5284b1
added a commit that references this issue on Mar 3, 2024

Auto merge of rust-lang#3334 - RalfJung:nullfix, r=RalfJung

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @brson@jesse99

        Issue actions

          document pipes vs comm · Issue #3334 · rust-lang/rust