https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=1.3.0 2015-01-08T16:02:24+00:00 2015-01-08T16:02:24+00:00 Huon Wilson dbau.pp+github@gmail.com 2015-01-08T10:54:35+00:00 urn:sha1:0c70ce1424f380360dcc8d857c68d2df1a27b6fd 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-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-03-21T12:37:21+00:00 Patrick Walton pcwalton@mimiga.net 2014-03-05T23:28:08+00:00 urn:sha1:af79a5aa7da4f42fc0939a19f46fa73b894d6e9a `~[T]` in test, libgetopts, compiletest, librustdoc, and libnum. 2014-03-21T12:37:21+00:00 Patrick Walton pcwalton@mimiga.net 2014-03-05T22:02:44+00:00 urn:sha1:579eb2400b3cb5d9cf03a5c8792d63630489193a 2014-03-14T20:59:02+00:00 Alex Crichton alex@alexcrichton.com 2014-03-14T18:16:10+00:00 urn:sha1:58e4ab2b33f559107dbdfa9d3cab882cf8029481 This commit shreds all remnants of libextra from the compiler and standard distribution. Two modules, c_vec/tempfile, were moved into libstd after some cleanup, and the other modules were moved to separate crates as seen fit. Closes #8784 Closes #12413 Closes #12576 2014-02-15T06:55:21+00:00 Alex Crichton alex@alexcrichton.com 2014-02-14T18:10:06+00:00 urn:sha1:a41b0c25295e06b8eebc4bdcb3021354f766cba0 This was previously implemented, and it just needed a snapshot to go through 2014-02-07T18:49:24+00:00 Derek Guenther dguenther9@gmail.com 2014-02-05T22:33:10+00:00 urn:sha1:730bdb6403dd47b98c1be6c4b3423edb28ca9477 2014-01-12T09:35:10+00:00 kud1ing github@kudling.de 2014-01-12T09:35:10+00:00 urn:sha1:871ffd1c050789c0bf2b3f6c2ab0069f3d2c0d66 2013-10-26T00:41:54+00:00 Brian Anderson banderson@mozilla.com 2013-10-25T21:28:38+00:00 urn:sha1:9a773da681a92c599f7b56f66f79bc107eeadbee These are relics that serve no purpose.