rust/src/libstd/sync, branch 1.0.0

Squeeze the last bits of `task`s in documentation in favor of `thread`

2015-05-11T17:05:21+00:00

An automated script was run against the `.rs` and `.md` files, subsituting every occurrence of `task` with `thread`. In the `.rs` files, only the texts in the comment blocks were affected.

Clarify Once::call_once memory ordering guarantees in docs

2015-05-10T19:20:07+00:00

Merge pull request #25192 from alexcrichton/beta-backport

2015-05-07T23:51:22+00:00

Backport of PRs to Beta

Make RwLock::try_write try to obtain a write lock

2015-05-07T21:39:17+00:00

Conflicts: src/libstd/sync/rwlock.rs

std: update select internals to not use mutable transmuting

2015-05-07T21:22:52+00:00

Add downcasting to std::error::Error

2015-05-05T17:57:01+00:00

This commit brings the `Error` trait in line with the [Error interoperation RFC](https://github.com/rust-lang/rfcs/pull/201) by adding downcasting, which has long been intended. This change means that for any `Error` trait objects that are `'static`, you can downcast to concrete error types. To make this work, it is necessary for `Error` to inherit from `Reflect` (which is currently used to mark concrete types as "permitted for reflection, aka downcasting"). This is a breaking change: it means that impls like ```rust impl Error for MyErrorType { ... } ``` must change to something like ```rust impl Error for MyErrorType { ... } ``` except that `Reflect` is currently unstable (and should remain so for the time being). For now, code can instead bound by `Any`: ```rust impl Error for MyErrorType { ... } ``` which *is* stable and has `Reflect` as a super trait. The downside is that this imposes a `'static` constraint, but that only constrains *when* `Error` is implemented -- it does not actually constrain the types that can implement `Error`. [breaking-change] Conflicts: src/libcore/marker.rs

std: Remove deprecated/unstable num functionality

2015-04-23T22:18:14+00:00

This commit removes all the old casting/generic traits from `std::num` that are no longer in use by the standard library. This additionally removes the old `strconv` module which has not seen much use in quite a long time. All generic functionality has been supplanted with traits in the `num` crate and the `strconv` module is supplanted with the [rust-strconv crate][rust-strconv]. [rust-strconv]: https://github.com/lifthrasiir/rust-strconv This is a breaking change due to the removal of these deprecated crates, and the alternative crates are listed above. [breaking-change] Conflicts: src/libstd/num/strconv.rs

pluralize doc comment verbs and add missing periods

2015-04-13T17:57:51+00:00

Indicate keyword in doc comment is code-like

2015-04-09T19:02:14+00:00

Auto merge of #24029 - nagisa:print-locking, r=alexcrichton

2015-04-08T19:03:09+00:00

write_fmt calls write for each formatted field. The default implementation of write_fmt is used, which will call write on not-yet-locked stdout (and write locking after), therefore making print! in multithreaded environment still interleave contents of two separate prints. I’m not sure whether we want to do this change, though, because it has the same deadlock hazard which we tried to avoid by not locking inside write_fmt itself (see [this comment](https://github.com/rust-lang/rust/blob/80def6c2447d23a624e611417f24cf0ab2a5a676/src/libstd/io/stdio.rs#L267)). Spotted on [reddit]. cc @alexcrichton [reddit]: http://www.reddit.com/r/rust/comments/31comh/println_with_multiple_threads/