https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=master 2018-05-17T19:25:24+00:00 2018-05-17T19:25:24+00:00 Mikela glassresistor@gmail.com 2018-05-17T19:25:24+00:00 urn:sha1:cfa26da963790dd59cdd6f6dc0005e83ccfc4ec5 2018-05-17T16:49:28+00:00 Mikela glassresistor@gmail.com 2018-05-17T16:49:28+00:00 urn:sha1:ec0d946b28f29eb779a81c8c7d42a46b76aab736 2015-01-14T02:11:47+00:00 Steve Klabnik steve@steveklabnik.com 2015-01-14T01:52:27+00:00 urn:sha1:40219249cf87585023e0d1b44de261dd56752142 Why redirect Tutorial -> Guide -> Book when you can just Tutorial -> Book? Suggested here: http://www.reddit.com/r/rust/comments/2schav/is_it_possible_to_automatically_redirect/ 2014-09-11T20:21:32+00:00 Steve Klabnik steve@steveklabnik.com 2014-08-21T21:43:48+00:00 urn:sha1:c456cca90ac3e2b2a853f3a9354d1e0c9fe6c427 2014-09-08T23:12:13+00:00 Patrick Walton pcwalton@mimiga.net 2014-09-06T22:23:55+00:00 urn:sha1:eb678ff87f0cdbf523b26fe9255cff684b4091e5 instead of prefix `..`. This breaks code that looked like: match foo { [ first, ..middle, last ] => { ... } } Change this code to: match foo { [ first, middle.., last ] => { ... } } RFC #55. Closes #16967. [breaking-change] 2014-08-18T16:19:10+00:00 Patrick Walton pcwalton@mimiga.net 2014-08-18T15:29:44+00:00 urn:sha1:67deb2e65e150a1b9b2fcd457da47e3e13b2c4f7 of `use bar as foo`. Change all uses of `use foo = bar` to `use bar as foo`. Implements RFC #47. Closes #16461. [breaking-change] 2014-08-11T19:31:16+00:00 Brian Anderson banderson@mozilla.com 2014-08-11T19:30:37+00:00 urn:sha1:21a70b38ba8aa3b50959c1b9f573391c7692611b cc #16123 2014-08-11T03:36:11+00:00 bors bors@rust-lang.org 2014-08-11T03:36:11+00:00 urn:sha1:4d27b4875e16ed6a4a0c9697432f1152b727e84a People reading the tutorial may not be familiar with the convention of naming lists, vectors and the like as xs, ys, etc. Without some explanation of the reasoning behind it, it might come off as just throwaway non-descriptive names. Languages like Haskell gets flak from using short, non-descriptive names, while in reality, there are clear conventions and reasons for using certain terse variable names. This is just a proposed explanation of this convention, as I've interpreted it - I assumed that the convention came from a language like Haskell, so I tailored it according to that. So beware that I might have misjudged how it is used in the Rust language, or at least how it is used in the Rust tutorial. 2014-08-10T20:51:22+00:00 LemmingAvalanche haugsbakk@yahoo.no 2014-07-04T11:19:42+00:00 urn:sha1:14e245bd47d3ac1a981d50a6f752aa27cca7d85e People reading the tutorial may not be familiar with the convention of naming lists, vectors and the like as xs, ys, etc. Without some explanation of the reasoning behind it, it might come off as just throwaway non-descriptive names. Languages like Haskell gets flak from using short, non-descriptive names, while in reality, there are clear conventions and reasons for using certain terse variable names. I assumed that the convention came from a language like Haskell, so I tailored the explanation according to that. 2014-08-08T03:51:15+00:00 bors bors@rust-lang.org 2014-08-08T03:51:15+00:00 urn:sha1:aae7901a78d5804306f7b20b01622d2a423db37c This leaves the `Share` trait at `std::kinds` via a `#[deprecated]` `pub use` statement, but the `NoShare` struct is no longer part of `std::kinds::marker` due to #12660 (the build cannot bootstrap otherwise). All code referencing the `Share` trait should now reference the `Sync` trait, and all code referencing the `NoShare` type should now reference the `NoSync` type. The functionality and meaning of this trait have not changed, only the naming. Closes #16281 [breaking-change]