rust/src/libstd/thread, branch 1.0.0-beta

rollup merge of #23860: nikomatsakis/copy-requires-clone

2015-04-02T01:37:54+00:00

Conflicts: src/test/compile-fail/coherence-impls-copy.rs

rollup merge of #23949: aturon/stab-timeout

2015-04-01T20:56:20+00:00

This commit renames and stabilizes: * `Condvar::wait_timeout_ms` (renamed from `wait_timeout`) * `thread::park_timeout_ms` (renamed from `park_timeout`) * `thread::sleep_ms` (renamed from `sleep`) In each case, the timeout is taken as a `u32` number of milliseconds, rather than a `Duration`. These functions are likely to be deprecated once a stable form of `Duration` is available, but there is little cost to having these named variants around, and it's crucial functionality for 1.0. [breaking-change] r? @alexcrichton cc @sfackler @carllerche

Stabilize basic timeout functionality

2015-04-01T20:43:45+00:00

Remove `Thunk` struct and `Invoke` trait; change `Thunk` to be an alias

2015-04-01T18:41:21+00:00

for `Box`. I found the alias was still handy because it is shorter than the fully written type. This is a [breaking-change]: convert code using `Invoke` to use `FnBox`, which is usually pretty straight-forward. Code using thunk mostly works if you change `Thunk::new => Box::new` and `foo.invoke(arg)` to `foo(arg)`.

Fallout in public-facing and semi-public-facing libs

2015-04-01T15:23:45+00:00

rollup merge of #23873: alexcrichton/remove-deprecated

2015-03-31T22:54:44+00:00

Conflicts: src/libcollectionstest/fmt.rs src/libcollectionstest/lib.rs src/libcollectionstest/str.rs src/libcore/error.rs src/libstd/fs.rs src/libstd/io/cursor.rs src/libstd/os.rs src/libstd/process.rs src/libtest/lib.rs src/test/run-pass-fulldeps/compiler-calls.rs

std: Clean out #[deprecated] APIs

2015-03-31T22:49:57+00:00

This commit cleans out a large amount of deprecated APIs from the standard library and some of the facade crates as well, updating all users in the compiler and in tests as it goes along.

std: Stabilize the rest of Any/BoxAny

2015-03-30T23:44:11+00:00

This commit stabilizes the following APIs: * `TypeId::of` - now that it has an `Any` bound it's ready to be stable. * `Box::downcast` - now that an inherent impl on `Box` as well as `Box` is allowed the `BoxAny` trait is removed in favor of these inherent methods. This is a breaking change due to the removal of the `BoxAny` trait, but consumers can simply remove imports to fix crates. [breaking-change]

rollup merge of #23752: alexcrichton/remove-should-fail

2015-03-27T17:07:48+00:00

This attribute has been deprecated in favor of #[should_panic]. This also updates rustdoc to no longer accept the `should_fail` directive and instead renames it to `should_panic`.

rollup merge of #23651: alexcrichton/unwind-try

2015-03-27T17:07:42+00:00

This commit provides a safe, but unstable interface for the `try` functionality of running a closure and determining whether it panicked or not. There are two primary reasons that this function was previously marked `unsafe`: 1. A vanilla version of this function exposes the problem of exception safety by allowing a bare try/catch in the language. It is not clear whether this concern should be directly tied to `unsafe` in Rust at the API level. At this time, however, the bounds on `ffi::try` require the closure to be both `'static` and `Send` (mirroring those of `thread::spawn`). It may be possible to relax the bounds in the future, but for now it's the level of safety that we're willing to commit to. 2. Panicking while panicking will leak resources by not running destructors. Because panicking is still controlled by the standard library, safeguards remain in place to prevent this from happening. The new API is now called `catch_panic` and is marked as `#[unstable]` for now.