rust/src/libstd/sync/mpmc_bounded_queue.rs, branch 0.11.0

sync: Move underneath libstd

2014-06-11T17:00:43+00:00

This commit is the final step in the libstd facade, #13851. The purpose of this commit is to move libsync underneath the standard library, behind the facade. This will allow core primitives like channels, queues, and atomics to all live in the same location. There were a few notable changes and a few breaking changes as part of this movement: * The `Vec` and `String` types are reexported at the top level of libcollections * The `unreachable!()` macro was copied to libcore * The `std::rt::thread` module was moved to librustrt, but it is still reexported at the same location. * The `std::comm` module was moved to libsync * The `sync::comm` module was moved under `sync::comm`, and renamed to `duplex`. It is now a private module with types/functions being reexported under `sync::comm`. This is a breaking change for any existing users of duplex streams. * All concurrent queues/deques were moved directly under libsync. They are also all marked with #![experimental] for now if they are public. * The `task_pool` and `future` modules no longer live in libsync, but rather live under `std::sync`. They will forever live at this location, but they may move to libsync if the `std::task` module moves as well. [breaking-change]

std: Remove UnsafeArc

2014-05-20T01:12:18+00:00

This type has been superseded by Arc>. The UnsafeArc type is a relic of an era that has long since past, and with the introduction of liballoc the standard library is able to use the Arc smart pointer. With little need left for UnsafeArc, it was removed. All existing code using UnsafeArc should either be reevaluated to whether it can use only Arc, or it should transition to Arc> [breaking-change]

std: Rebuild mpmc queues on Unsafe/Arc

2014-05-19T23:01:48+00:00

This removes usage of UnsafeArc and uses proper self mutability for concurrent types.

Test fixes and rebase conflicts

2014-05-07T18:03:12+00:00

std,serialize: remove some internal uses of ~[].

2014-04-10T22:21:58+00:00

These are all private uses of ~[], so can easily & non-controversially be replaced with Vec.

std: Switch field privacy as necessary

2014-03-31T22:17:12+00:00

Convert most code to new inner attribute syntax.

2014-03-29T00:12:21+00:00

Closes #2569

rename std::vec -> std::slice

2014-03-20T05:30:27+00:00

Closes #12702

std: Rename Chan/Port types and constructor

2014-03-13T20:23:29+00:00

* Chan => Sender * Port => Receiver * Chan::new() => channel() * constructor returns (Sender, Receiver) instead of (Receiver, Sender) * local variables named `port` renamed to `rx` * local variables named `chan` renamed to `tx` Closes #11765

Rewrite channels yet again for upgradeability

2014-02-12T00:32:00+00:00

This, the Nth rewrite of channels, is not a rewrite of the core logic behind channels, but rather their API usage. In the past, we had the distinction between oneshot, stream, and shared channels, but the most recent rewrite dropped oneshots in favor of streams and shared channels. This distinction of stream vs shared has shown that it's not quite what we'd like either, and this moves the `std::comm` module in the direction of "one channel to rule them all". There now remains only one Chan and one Port. This new channel is actually a hybrid oneshot/stream/shared channel under the hood in order to optimize for the use cases in question. Additionally, this also reduces the cognitive burden of having to choose between a Chan or a SharedChan in an API. My simple benchmarks show no reduction in efficiency over the existing channels today, and a 3x improvement in the oneshot case. I sadly don't have a pre-last-rewrite compiler to test out the old old oneshots, but I would imagine that the performance is comparable, but slightly slower (due to atomic reference counting). This commit also brings the bonus bugfix to channels that the pending queue of messages are all dropped when a Port disappears rather then when both the Port and the Chan disappear.