https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=try 2014-11-21T01:19:13+00:00 2014-11-21T01:19:13+00:00 Aaron Turon aturon@mozilla.com 2014-11-14T21:55:57+00:00 urn:sha1:3ee916e50bd86768cb2a9141f9b2c52d2601b412 With runtime removal complete, there's nothing left of libnative. This commit removes it. Fixes #18687 [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-31T00:37:22+00:00 Alex Crichton alex@alexcrichton.com 2014-10-30T16:02:07+00:00 urn:sha1:00975e041d42b89b14b2655b2891e3348f3ad3f1 Conflicts: src/libcollections/slice.rs src/libcore/failure.rs src/libsyntax/parse/token.rs src/test/debuginfo/basic-types-mut-globals.rs src/test/debuginfo/simple-struct.rs src/test/debuginfo/trait-pointers.rs 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-28T15:54:21+00:00 Aaron Turon aturon@mozilla.com 2014-10-27T22:37:07+00:00 urn:sha1:e0ad0fcb95f0bd6e69e9032c23b66515a590dfe5 2014-10-24T12:36:29+00:00 John Kåre Alsaker john.kare.alsaker@gmail.com 2014-10-23T05:29:41+00:00 urn:sha1:70cef9474a3307ec763efc01fe6969e542083823 Fixes #17562 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-16T15:15:34+00:00 Luqman Aden laden@csclub.uwaterloo.ca 2014-10-15T01:07:11+00:00 urn:sha1:38aca17c474321e4c260e36f173275a90d753397 2014-10-09T17:50:13+00:00 Brian Anderson banderson@mozilla.com 2014-10-09T17:47:22+00:00 urn:sha1:5c92a8e054d508c260653386bd4861d249a6e09a