https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=1.1.0 2015-04-09T00:21:34+00:00 2015-04-09T00:21:34+00:00 Alex Crichton alex@alexcrichton.com 2015-04-08T23:27:10+00:00 urn:sha1:ec7c800d2fc0dc5918d325ae68d88c9708d20259 This commit removes pretty-expanded from all tests that wind up calling panic! one way or another now that its internals are unstable. 2015-03-23T21:40:26+00:00 Brian Anderson banderson@mozilla.com 2015-03-22T20:13:15+00:00 urn:sha1:8c93a79e387f5197e8b8fe73b3d87d2b101b7c4a Now that features must be declared expanded source often does not compile. This adds 'pretty-expanded' to a bunch of test cases that still work. 2015-01-30T03:38:54+00:00 Tobias Bucher tobiasbucher5991@gmail.com 2015-01-25T21:05:03+00:00 urn:sha1:7f64fe4e27555c256cb228feb05d4181a2287125 2015-01-08T01:31:37+00:00 Felix S. Klock II pnkfelix@pnkfx.org 2015-01-08T01:25:56+00:00 urn:sha1:a7a2dd96ecc62221f78013abb3269591f4d07f04 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-10-02T14:02:15+00:00 Eduard Burtescu edy.burt@gmail.com 2014-10-02T05:10:09+00:00 urn:sha1:58bea31ca0e11bf49439d33e1d21f11de7161567 2014-07-27T04:05:29+00:00 Brian Anderson banderson@mozilla.com 2014-07-27T04:05:03+00:00 urn:sha1:aa486547404553227fa3db0a887554245605075a No longer does anything. 2014-06-29T18:47:58+00:00 Patrick Walton pcwalton@mimiga.net 2014-06-27T19:30:25+00:00 urn:sha1:a5bb0a3a4574af88add700ace7aefc37172fa7a5 floating point numbers for real. This will break code that looks like: let mut x = 0; while ... { x += 1; } println!("{}", x); Change that code to: let mut x = 0i; while ... { x += 1; } println!("{}", x); Closes #15201. [breaking-change] 2014-06-14T17:45:37+00:00 Alex Crichton alex@alexcrichton.com 2014-06-12T02:33:52+00:00 urn:sha1:ade807c6dcf6dc4454732c5e914ca06ebb429773 This removes all remnants of `@` pointers from rustc. Additionally, this removes the `GC` structure from the prelude as it seems odd exporting an experimental type in the prelude by default. Closes #14193 [breaking-change]