Skip to content

pipes::chan should also expose try_send #3134

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.

Sign up for GitHub

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

Jump to bottom
Closed
eholk opened this issue Aug 7, 2012 · 1 comment
Closed

pipes::chan should also expose try_send #3134

eholk opened this issue Aug 7, 2012 · 1 comment
Labels
A-concurrency Area: Concurrency C-enhancement Category: An issue proposing an enhancement or a PR with one.

Comments

@eholk
Copy link
Contributor

eholk commented Aug 7, 2012

The protocol compiler has the support necessary to do this now, but we'll need a snapshot before we can implement this.
@eholk
Copy link
Contributor Author

eholk commented Aug 13, 2012

This is now implemented.

@eholk eholk closed this as completed Aug 13, 2012
bors pushed a commit to rust-lang-ci/rust that referenced this issue May 15, 2021
@nrc
Merge pull request rust-lang#3134 from otavio/issue-3104
284583f 
Stabilize `edition` configuration option
RalfJung pushed a commit to RalfJung/rust that referenced this issue Oct 25, 2023
@bors
Auto merge of rust-lang#3134 - RalfJung:log-not-lin, r=saethlin
74092c5 
avoid a linear scan over the entire int_to_ptr_map on each deallocation
celinval pushed a commit to celinval/rust-dev that referenced this issue Jun 4, 2024
@tautschnig
Do not assume that ZST-typed symbols refer to unique objects (rust-la…
9e34364 
…ng#3134)

The Rust specification does not guarantee that ZST-typed symbols are
backed by unique objects, and `rustc` appears to make use of this as can
be demonstrated for both locals and statics. For parameters no such
example has been found, but as there remains a lack of a guarantee we
err on the safe side.

Resolves: rust-lang#3129
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-concurrency Area: Concurrency C-enhancement Category: An issue proposing an enhancement or a PR with one.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@eholk