| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2018-09-05 | Remove `#[repr(transparent)]` from atomics | Alex Crichton | -3/+0 | |
| Added in #52149 the discussion in #53514 is showing how we may not want to actually add this attribute to the atomic types. While we continue to debate #53514 this commit reverts the addition of the `transparent` attribute. This should be a more conservative route which leaves us the ability to tweak this in the future but in the meantime allows us to continue discussion as well. | ||||
| 2018-08-15 | Make core::sync::atomic::Ordering #[non_exhaustive] | varkor | -24/+1 | |
| 2018-08-07 | document mode possibilities for all RMW operations | Ralf Jung | -29/+226 | |
| 2018-08-07 | list possible orderings for load and store | Ralf Jung | -26/+43 | |
| 2018-08-07 | forgot to add comment for some atomic types | Ralf Jung | -2/+4 | |
| 2018-08-07 | fix link label; use more https | Ralf Jung | -14/+14 | |
| 2018-08-06 | atomic ordering docs | Ralf Jung | -11/+48 | |
| 2018-08-01 | Switch to bootstrapping from 1.29 beta | Mark Rousskov | -16/+16 | |
| 2018-07-07 | Add #[repr(transparent)] to Atomic* types | willmo | -0/+3 | |
| This allows them to be used in #[repr(C)] structs without warnings. Since rust-lang/rfcs#1649 and rust-lang/rust#35603 they are already documented to have "the same in-memory representation as" their corresponding primitive types. This just makes that explicit. | ||||
| 2018-07-05 | #[cfg(target_has_atomic_cas)] -> #[cfg(target_has_atomic = "cas")] | Jorge Aparicio | -16/+16 | |
| 2018-07-05 | enable Atomic*.{load,store} for ARMv6-M / MSP430 | Jorge Aparicio | -0/+16 | |
| closes #45085 this commit adds an `atomic_cas` target option and an unstable `#[cfg(target_has_atomic_cas)]` attribute to enable a subset of the `Atomic*` API on architectures that don't support atomic CAS natively, like MSP430 and ARMv6-M. | ||||
| 2018-04-19 | Auto merge of #48553 - seanmonstar:atomic-debug, r=alexcrichton | bors | -5/+3 | |
| atomic: remove 'Atomic*' from Debug output For the same reason that we don't show `Vec { data: [0, 1, 2, 3] }`, but just the array, the `AtomicUsize(1000)` is noisy, and seeing just `1000` is likely better. | ||||
| 2018-04-16 | Auto merge of #49963 - llogiq:stabilize-13226, r=kennytm | bors | -12/+11 | |
| stabilize fetch_nand This closes #13226 and makes `Atomic*.fetch_nand` stable. | ||||
| 2018-04-14 | stabilize fetch_nand | Andre Bogus | -12/+11 | |
| 2018-04-12 | improve Atomic*::fetch_update docs | Andre Bogus | -2/+2 | |
| 2018-04-05 | Rollup merge of #48658 - llogiq:no-more-cas, r=kennytm | kennytm | -0/+185 | |
| Add a generic CAS loop to std::sync::Atomic* This adds two new methods to both `AtomicIsize` and `AtomicUsize` with optimized safe compare-and-set loops, so users will no longer need to write their own, except in *very* strange circumstances. `update_and_fetch` will apply the function and return its result, whereas `fetch_and_update` will apply the function and return the previous value. This solves #48384 with `x.update_and_fetch(|x| x.max(y))`. It also relates to #48655 (which I misuse as tracking issue for now).. *note* This *might* need a crater run because the functions could clash with third party extension traits. | ||||
| 2018-03-30 | Add a generic CAS loop to std::sync::Atomic* | Andre Bogus | -0/+185 | |
| This adds a new method to all numeric `Atomic*` types with a safe compare-and-set loop, so users will no longer need to write their own, except in *very* strange circumstances. This solves #48384 with `x.fetch_max(_)`/`x.fetch_min(_)`. It also relates to #48655 (which I misuse as tracking issue for now). *note* This *might* need a crater run because the functions could clash with third party extension traits. | ||||
| 2018-03-26 | Rollup merge of #49170 - steveklabnik:gh49127, r=nagisa | Tim Neumann | -2/+5 | |
| Clarify AcqRel's docs This implied things that are not true. Fixes #49127 | ||||
| 2018-03-25 | update wording as per feedback | Steve Klabnik | -1/+3 | |
| 2018-03-19 | Make Atomic doc examples specific to each type | Guillaume Gomez | -364/+401 | |
| 2018-03-19 | Clarify AcqRel's docs | steveklabnik | -2/+3 | |
| This implied things that are not true. Fixes #49127 | ||||
| 2018-02-26 | atomic: remove 'Atomic*' from Debug output | Sean McArthur | -5/+3 | |
| 2018-02-16 | Force the link to std::thread::yield_now() | Stefan Schindler | -1/+1 | |
| 2018-02-16 | Add link to yield_now | Stefan Schindler | -3/+4 | |
| 2018-02-09 | Add fetch_nand. | Mark Simulacrum | -0/+46 | |
| cc #13226 (the tracking issue) | ||||
| 2018-01-28 | Auto merge of #47204 - varkor:unsafecell-into_inner-safe, r=alexcrichton | bors | -3/+3 | |
| Make UnsafeCell::into_inner safe This fixes #35067. It will require a Crater run as discussed in that issue. | ||||
| 2018-01-05 | Make UnsafeCell::into_inner safe | varkor | -3/+3 | |
| This fixes #35067. It will require a Crater run as discussed in that issue. | ||||
| 2017-12-27 | Correct a few stability attributes | Oliver Middleton | -1/+12 | |
| 2017-12-10 | Add `std::fmt::Pointer` implementation for `AtomicPtr` | varkor | -0/+8 | |
| Resolves #29212. | ||||
| 2017-11-29 | Rollup merge of #46293 - ollie27:atomic_bool_from, r=BurntSushi | kennytm | -0/+7 | |
| impl From<bool> for AtomicBool This seems like an obvious omission from #45610. ~~I've used the same feature name and version in the hope that this can be backported to beta so it's stabilized with the other impls. If it can't be I'll change it to `1.24.0`.~~ | ||||
| 2017-11-29 | Rollup merge of #46287 - SimonSapin:stable-constness, r=aturon | kennytm | -14/+1 | |
| Stabilize const-calling existing const-fns in std Fixes #46038 | ||||
| 2017-11-27 | Change version number for `impl From<bool> for AtomicBool` to 1.24.0 | Oliver Middleton | -1/+1 | |
| 2017-11-27 | Change the stabilization version to 1.24.0 | Stjepan Glavina | -1/+1 | |
| 2017-11-27 | impl From<bool> for AtomicBool | Oliver Middleton | -0/+7 | |
| 2017-11-26 | Stabilize const-calling existing const-fns in std | Simon Sapin | -14/+1 | |
| Fixes #46038 | ||||
| 2017-11-22 | Stabilize spin_loop_hint | Stjepan Glavina | -3/+2 | |
| 2017-11-09 | fix core for targets with max-atomic-width = 0 | Jorge Aparicio | -0/+1 | |
| closes #45802 | ||||
| 2017-10-31 | since = "1.23.0" | M Farkas-Dyck | -2/+2 | |
| 2017-10-29 | feature = "atomic_from" | M Farkas-Dyck | -2/+2 | |
| 2017-10-29 | impl From<T> for AtomicT | M Farkas-Dyck | -0/+12 | |
| 2017-10-26 | Bump to 1.23 and update bootstrap | Alex Crichton | -3/+3 | |
| This commit updates the bootstrap compiler, bumps the version to 1.23, updates Cargo, updates books, and updates crates.io dependencies | ||||
| 2017-10-05 | Add missing links for AtomicBool | Guillaume Gomez | -5/+12 | |
| 2017-09-29 | Rollup merge of #44854 - lucasem:atomic-docs, r=steveklabnik | Mark Simulacrum | -1/+25 | |
| docs improvement sync::atomic::Atomic* Addresses the `Atomic*` part of #29377. r? @steveklabnik | ||||
| 2017-09-25 | docs improvement sync::atomic::Atomic* | Lucas Morales | -1/+25 | |
| 2017-09-24 | Backport libs stabilizations to 1.21 beta | David Tolnay | -1/+1 | |
| This includes the following stabilizations: - tcpstream_connect_timeout https://github.com/rust-lang/rust/pull/44563 - iterator_for_each https://github.com/rust-lang/rust/pull/44567 - ord_max_min https://github.com/rust-lang/rust/pull/44593 - compiler_fences https://github.com/rust-lang/rust/pull/44595 - needs_drop https://github.com/rust-lang/rust/pull/44639 - vec_splice https://github.com/rust-lang/rust/pull/44640 | ||||
| 2017-09-16 | Added more text from unstable-book to `compiler_fence` docs | Michal Budzynski | -4/+19 | |
| 2017-09-16 | Added example to `compiler_fence` docs taken from unstable-book | Michal Budzynski | -0/+34 | |
| 2017-09-16 | stabilized compiler_fences (fixes #41091) | Michal Budzynski | -1/+1 | |
| 2017-09-16 | change #![feature(const_fn)] to specific gates | Alex Burka | -1/+14 | |
| 2017-08-15 | Fix typos & us spellings | Fourchaux | -1/+1 | |
