https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=try 2015-05-07T16:30:00+00:00 2015-05-07T16:30:00+00:00 Alex Crichton alex@alexcrichton.com 2015-05-05T23:39:46+00:00 urn:sha1:a031325e83b8f050f840395239197ea87361ada5 This module has been removed for quite some time! 2015-03-26T19:10:22+00:00 Alex Crichton alex@alexcrichton.com 2015-03-26T00:06:52+00:00 urn:sha1:43bfaa4a336095eb5697fb2df50909fd3c72ed14 Now that support has been removed, all lingering use cases are renamed. 2015-03-24T22:27:14+00:00 Alex Crichton alex@alexcrichton.com 2015-03-24T22:27:14+00:00 urn:sha1:3b13b9c2b4e72d08cb1c68024ccc4f50001f4878 Reject specialized Drop impls. See Issue #8142 for discussion. This makes it illegal for a Drop impl to be more specialized than the original item. So for example, all of the following are now rejected (when they would have been blindly accepted before): ```rust struct S<A> { ... }; impl Drop for S<i8> { ... } // error: specialized to concrete type struct T<'a> { ... }; impl Drop for T<'static> { ... } // error: specialized to concrete region struct U<A> { ... }; impl<A:Clone> Drop for U<A> { ... } // error: added extra type requirement struct V<'a,'b>; impl<'a,'b:a> Drop for V<'a,'b> { ... } // error: added extra region requirement ``` Due to examples like the above, this is a [breaking-change]. (The fix is to either remove the specialization from the `Drop` impl, or to transcribe the requirements into the struct/enum definition; examples of both are shown in the PR's fixed to `libstd`.) ---- This is likely to be the last thing blocking the removal of the `#[unsafe_destructor]` attribute. Fix #8142 Fix #23584 2015-03-24T21:27:22+00:00 Felix S. Klock II pnkfelix@pnkfx.org 2015-03-21T12:14:28+00:00 urn:sha1:0adab507bbb0b04fe389a00af19fc17753b76343 This was necessary to avoid specialized `Drop` impls for the two structs. 2015-03-21T18:14:58+00:00 Alex Crichton alex@alexcrichton.com 2015-03-21T18:08:15+00:00 urn:sha1:1ec9adcfc0da7b1cdfe8d42f7eedcbd727c6861c There have been some recent panics on the bots and this commit is an attempt to appease them. Previously it was considered invalid to run `rt::at_exit` after the handlers had already started running. Due to the multithreaded nature of applications, however, it is not always possible to guarantee this. For example [this program][ex] will show off the abort. [ex]: https://gist.github.com/alexcrichton/56300b87af6fa554e52d The semantics of the `rt::at_exit` function have been modified as such: * It is now legal to call `rt::at_exit` at any time. The return value now indicates whether the closure was successfully registered or not. Callers must now decide what to do with this information. * The `rt::at_exit` handlers will now be run for a fixed number of iterations. Common cases (such as the example shown) may end up registering a new handler while others are running perhaps once or twice, so this common condition is covered by re-running the handlers a fixed number of times, after which new registrations are forbidden. Some usage of `rt::at_exit` was updated to handle these new semantics, but deprecated or unstable libraries calling `rt::at_exit` were not updated. 2015-03-20T17:56:27+00:00 Alex Crichton alex@alexcrichton.com 2015-01-01T18:19:42+00:00 urn:sha1:1cc9718fdef63476ffdf3f0bcd74b554b083f378 This reverts commit aec67c2ee0f673ea7b0e21c2fe7e0f26a523d823. 2015-03-12T17:23:27+00:00 Alex Crichton alex@alexcrichton.com 2015-03-10T03:04:35+00:00 urn:sha1:c933d44f7bb908aa520250b608f85bfacfccc337 These were suppressing lots of interesting warnings! Turns out there was also quite a bit of dead code. 2015-02-22T23:59:17+00:00 Stepan Koltsov stepan.koltsov@gmail.com 2015-02-22T23:58:22+00:00 urn:sha1:26d9f0ab1aeb3d7b440911104cf17741f83aa0f5 ... to convert between Box and raw pointers. E. g. use ``` let b: Box<Foo> = Box::from_raw(p); ``` instead of ``` let b: Box<Foo> = mem::transmute(p); ``` Patch also changes closure release code in `src/libstd/sys/unix/thread.rs` when `pthread_create` failed. Raw pointer was transmuted to box of `FnOnce()` instead of `Thunk`. This code was probably never executed, because `pthread_create` rarely fails in practice. 2015-02-18T01:32:16+00:00 Alex Crichton alex@alexcrichton.com 2015-02-18T01:32:16+00:00 urn:sha1:ba8ce4c2c27643cccfbbc481a19bcf4b7747cc89 Conflicts: src/libstd/sync/task_pool.rs src/libstd/thread.rs src/libtest/lib.rs src/test/bench/shootout-reverse-complement.rs src/test/bench/shootout-spectralnorm.rs 2015-02-17T23:14:17+00:00 Aaron Turon aturon@mozilla.com 2015-02-17T23:10:25+00:00 urn:sha1:d0de2b46e9bcca93971ef64d6ecdef872633f246