https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=try 2014-11-21T01:19:24+00:00 2014-11-21T01:19:24+00:00 Aaron Turon aturon@mozilla.com 2014-11-14T21:56:15+00:00 urn:sha1:91a2c0d51241677d71b8c0abc80535e580fe3939 With runtime removal complete, there is no longer any reason to provide libgreen. [breaking-change] 2014-11-17T15:35:51+00:00 Steven Fackler sfackler@gmail.com 2014-11-06T08:05:53+00:00 urn:sha1:3dcd2157403163789aaf21a9ab3c4d30a7c6494d This breaks code that referred to variant names in the same namespace as their enum. Reexport the variants in the old location or alter code to refer to the new locations: ``` pub enum Foo { A, B } fn main() { let a = A; } ``` => ``` pub use self::Foo::{A, B}; pub enum Foo { A, B } fn main() { let a = A; } ``` or ``` pub enum Foo { A, B } fn main() { let a = Foo::A; } ``` [breaking-change] 2014-11-09T04:40:39+00:00 Aaron Turon aturon@mozilla.com 2014-10-17T20:39:27+00:00 urn:sha1:fa94fdad3e880d2d6cbd82c12bd12caefbeb81a8 This patch cleans up the remnants of the runtime IO interface. Because this eliminates APIs in `libnative` and `librustrt`, it is a: [breaking-change] This functionality is likely to be available publicly, in some form, from `std` in the future. 2014-10-29T15:43:07+00:00 Steve Klabnik steve@steveklabnik.com 2014-10-09T19:17:22+00:00 urn:sha1:7828c3dd2858d8f3a0448484d8093e22719dbda0 https://github.com/rust-lang/rfcs/pull/221 The current terminology of "task failure" often causes problems when writing or speaking about code. You often want to talk about the possibility of an operation that returns a Result "failing", but cannot because of the ambiguity with task failure. Instead, you have to speak of "the failing case" or "when the operation does not succeed" or other circumlocutions. Likewise, we use a "Failure" header in rustdoc to describe when operations may fail the task, but it would often be helpful to separate out a section describing the "Err-producing" case. We have been steadily moving away from task failure and toward Result as an error-handling mechanism, so we should optimize our terminology accordingly: Result-producing functions should be easy to describe. To update your code, rename any call to `fail!` to `panic!` instead. Assuming you have not created your own macro named `panic!`, this will work on UNIX based systems: grep -lZR 'fail!' . | xargs -0 -l sed -i -e 's/fail!/panic!/g' You can of course also do this by hand. [breaking-change] 2014-10-19T19:59:40+00:00 Alex Crichton alex@alexcrichton.com 2014-10-15T06:05:01+00:00 urn:sha1:9d5d97b55d6487ee23b805bc1acbaa0669b82116 Spring cleaning is here! In the Fall! This commit removes quite a large amount of deprecated functionality from the standard libraries. I tried to ensure that only old deprecated functionality was removed. This is removing lots and lots of deprecated features, so this is a breaking change. Please consult the deprecation messages of the deleted code to see how to migrate code forward if it still needs migration. [breaking-change] 2014-10-02T22:43:37+00:00 Alex Crichton alex@alexcrichton.com 2014-10-02T22:12:58+00:00 urn:sha1:f96ee10e888bac4435973972f1799db509b3318e 2014-09-30T21:38:04+00:00 Patrick Walton pcwalton@mimiga.net 2014-09-23T23:07:21+00:00 urn:sha1:496cc4c0d4a06047c4f78965c8bc6e2c812c7812 prefer `Deref` over `DerefMut` in all other circumstances. Closes #12825. 2014-09-16T21:37:48+00:00 Aaron Turon aturon@mozilla.com 2014-09-15T03:27:36+00:00 urn:sha1:fc525eeb4ec3443d29bce677f589b19f31c189bb 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] 2014-06-25T00:18:48+00:00 Niko Matsakis niko@alum.mit.edu 2014-04-21T21:58:52+00:00 urn:sha1:9e3d0b002a5c2e81d43351c9b8550a3f4ccfb8f9 This breaks a fair amount of code. The typical patterns are: * `for _ in range(0, 10)`: change to `for _ in range(0u, 10)`; * `println!("{}", 3)`: change to `println!("{}", 3i)`; * `[1, 2, 3].len()`: change to `[1i, 2, 3].len()`. RFC #30. Closes #6023. [breaking-change]