Add send_any for pipes #3018
Labels
A-concurrency
Area: Concurrency
C-enhancement
Category: An issue proposing an enhancement or a PR with one.
E-easy
Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
P-low
Low priority
Comments
ghost
assigned 
|
compared to #3020, this one is even more obviously user-implementable and doesn't need to be a primitive. I feel like this can be closed. |
Closed
|
see discussion in #3020; this is worth leaving open |
bors
added a commit
that referenced
this issue
Aug 1, 2013
The pipes compiler produced data types that encoded efficient and safe bounded message passing protocols between two endpoints. It was also capable of producing unbounded protocols. It was useful research but was arguably done before its proper time. I am removing it for the following reasons: * In practice we used it only for producing the `oneshot` protcol and the unbounded `stream` protocol and all communication in Rust use those. * The interface between the proto! macro and the standard library has a large surface area and was difficult to maintain through language and library changes. * It is now written in an old dialect of Rust and generates code which would likely be considered non-idiomatic. * Both the compiler and the runtime are difficult to understand, and likewise the relationship between the generated code and the library is hard to understand. Debugging is difficult. * The new scheduler implements `stream` and `oneshot` by hand in a way that will be significantly easier to maintain. This shouldn't be taken as an indication that 'channel protocols' for Rust are not worth pursuing again in the future. Concerned parties may include: @graydon, @pcwalton, @eholk, @bblum The most likely candidates for closing are #7666, #3018, #3020, #7021, #7667, #7303, #3658, #3295.
|
This doesn't have to do with the pipe compiler; it's just a convenience function that could work for new runtime pipes as well. |
Closed
|
Accepting P-low. |
|
I'm not sure what this should do (how the sender is picked): if this function were on |
|
Closing. See this comment: #3020 (comment) |
RalfJung
pushed a commit
to RalfJung/rust
that referenced
this issue
Aug 17, 2023
[nit][typo] Fix out of order words.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Part of #1255.
This would take a list of chans and a message and send it on one of them.
I'm not entirely sure how this is useful, but we did have a request for it.
The text was updated successfully, but these errors were encountered: