https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=1.6.0 2015-08-18T02:35:52+00:00 2015-08-18T02:35:52+00:00 Alex Crichton alex@alexcrichton.com 2015-08-17T21:16:41+00:00 urn:sha1:a2b932c0b614aa5a68f7d24977fab241998a89ef Stop using stability to hide the implementation details of ParseFloatError and instead move the error type into the `dec2flt` module. Also move the implementation blocks of `FromStr for f{32,64}` into `dec2flt` directly. 2015-05-27T08:19:03+00:00 Eduard Burtescu edy.burt@gmail.com 2015-05-27T08:18:36+00:00 urn:sha1:377b0900aede976b2d37a499bbd7b62c2e39b358 2015-01-11T19:47:44+00:00 Steven Fackler sfackler@gmail.com 2015-01-10T21:42:48+00:00 urn:sha1:8b6cda3ce681d4d95c3097d12ed754975b4a07f6 Change any use of AtomicInt to AtomicIsize and AtomicUint to AtomicUsize Closes #20893 [breaking-change] 2015-01-02T06:02:59+00:00 Alex Crichton alex@alexcrichton.com 2014-12-29T23:03:01+00:00 urn:sha1:f3a7ec7028c76b3a1c6051131328f372b068e33a This pass performs a second pass of stabilization through the `std::sync` module, avoiding modules/types that are being handled in other PRs (e.g. mutexes, rwlocks, condvars, and channels). The following items are now stable * `sync::atomic` * `sync::atomic::ATOMIC_BOOL_INIT` (was `INIT_ATOMIC_BOOL`) * `sync::atomic::ATOMIC_INT_INIT` (was `INIT_ATOMIC_INT`) * `sync::atomic::ATOMIC_UINT_INIT` (was `INIT_ATOMIC_UINT`) * `sync::Once` * `sync::ONCE_INIT` * `sync::Once::call_once` (was `doit`) * C == `pthread_once(..)` * Boost == `call_once(..)` * Windows == `InitOnceExecuteOnce` * `sync::Barrier` * `sync::Barrier::new` * `sync::Barrier::wait` (now returns a `bool`) * `sync::Semaphore::new` * `sync::Semaphore::acquire` * `sync::Semaphore::release` The following items remain unstable * `sync::SemaphoreGuard` * `sync::Semaphore::access` - it's unclear how this relates to the poisoning story of mutexes. * `sync::TaskPool` - the semantics of a failing task and whether a thread is re-attached to a thread pool are somewhat unclear, and the utility of this type in `sync` is question with respect to the jobs of other primitives. This type will likely become stable or move out of the standard library over time. * `sync::Future` - futures as-is have yet to be deeply re-evaluated with the recent core changes to Rust's synchronization story, and will likely become stable in the future but are unstable until that time comes. [breaking-change] 2014-12-31T16:33:13+00:00 Alex Crichton alex@alexcrichton.com 2014-12-31T00:29:27+00:00 urn:sha1:582cba183f18eea5c40b6c035d63ad449a9e8604 2014-10-11T05:09:49+00:00 Alex Crichton alex@alexcrichton.com 2014-10-11T04:59:10+00:00 urn:sha1:dae48a07f34dcf714b3b57029f4e03a0b95a269e Also convert a number of `static mut` to just a plain old `static` and remove some unsafe blocks. 2014-08-04T23:03:21+00:00 Aaron Turon aturon@mozilla.com 2014-08-04T22:42:36+00:00 urn:sha1:68bde0a07396efb415d61047c6b2a8183f47ef30 This commit stabilizes the `std::sync::atomics` module, renaming it to `std::sync::atomic` to match library precedent elsewhere, and tightening up behavior around incorrect memory ordering annotations. The vast majority of the module is now `stable`. However, the `AtomicOption` type has been deprecated, since it is essentially unused and is not truly a primitive atomic type. It will eventually be replaced by a higher-level abstraction like MVars. Due to deprecations, this is a: [breaking-change]