| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2014-10-07 | auto merge of #17832 : brson/rust/updateversion, r=alexcrichton | bors | -1/+1 | |
| 2014-10-07 | Put slicing syntax behind a feature gate. | Nick Cameron | -1/+1 | |
| [breaking-change] If you are using slicing syntax you will need to add #![feature(slicing_syntax)] to your crate. | ||||
| 2014-10-06 | doc: Update output of `rustc --version` | Brian Anderson | -1/+1 | |
| 2014-10-04 | docs: Reference hoedown instead of sundown | Brian Campbell | -2/+2 | |
| 2014-10-04 | auto merge of #17754 : O-I/rust/update-guide, r=steveklabnik | bors | -17/+16 | |
| Hi, These are a few small edits to the Guide that I made while reading online. Really well done and approachable. I have a few questions below, but I don't know if this is the proper place to ask them, so feel free to ignore the below. 1. Trailing commas seem to be a convention in Rust and are used quite a bit throughout the Guide, but are never explicitly mentioned. Maybe adding a short mention about them when they first appear in the Structs section might be helpful to those who are unfamiliar with or don't use them in other languages. 2. In the Iterators section, there is a block of code like this: ```rust let mut range = range(0i, 10i); loop { match range.next() { Some(x) => { println!("{}", x); } // no comma needed? None => { break } } } ``` My inclination would be to put a comma where the comment is to separate the two arms to get this to compile, but it runs fine either way. Is there a convention on commas for scenarios like this where each arm is enclosed in `{}`? All the best, O-I | ||||
| 2014-10-03 | auto merge of #17743 : steveklabnik/rust/receiver_fix, r=alexcrichton | bors | -1/+1 | |
| 2014-10-03 | Adds comma | Rahul Horé | -1/+1 | |
| Oddly (to me), this code runs fine without the comma separating the `Some` and `None` arms of the `match` construct. It seems like Rust doesn't require you to separate arms with commas if all the expressions are enclosed in braces. | ||||
| 2014-10-03 | Fixes wording | Rahul Horé | -2/+2 | |
| 2014-10-03 | Removes extra . | Rahul Horé | -1/+1 | |
| 2014-10-03 | Adds missing cd | Rahul Horé | -1/+2 | |
| 2014-10-03 | Test fixes from the rollup | Alex Crichton | -1/+1 | |
| 2014-10-03 | Use similar syntax in all arms | Rahul Horé | -7/+5 | |
| See issue #17672. This was started in commit ee1cbb9c71bfab8500dfabedb35ba63dd1e5b7ff, but there were a few more lines to update. | ||||
| 2014-10-03 | Fixes output | Rahul Horé | -1/+1 | |
| 2014-10-03 | Adds trailing comma | Rahul Horé | -2/+2 | |
| 2014-10-03 | Fixes spacing | Rahul Horé | -2/+2 | |
| 2014-10-03 | Update signature of try_recv() | Steve Klabnik | -1/+1 | |
| 2014-10-03 | auto merge of #16995 : kmcallister/rust/plugin-tutorial, r=alexcrichton | bors | -15/+371 | |
| @steveklabnik, are you interested in looking this over? | ||||
| 2014-10-02 | rollup merge of #17666 : eddyb/take-garbage-out | Alex Crichton | -18/+2 | |
| Conflicts: src/libcollections/lib.rs src/libcore/lib.rs src/librustdoc/lib.rs src/librustrt/lib.rs src/libserialize/lib.rs src/libstd/lib.rs src/test/run-pass/issue-8898.rs | ||||
| 2014-10-02 | rollup merge of #17717 : steveklabnik/gh17190 | Alex Crichton | -3/+5 | |
| 2014-10-02 | rollup merge of #17698 : jistr/guide_export | Alex Crichton | -3/+3 | |
| 2014-10-02 | rollup merge of #17695 : steveklabnik/various_docs | Alex Crichton | -20/+14 | |
| 2014-10-02 | extra comment about macros | Steve Klabnik | -3/+5 | |
| Fixes #17190 | ||||
| 2014-10-02 | I am bad at math | Steve Klabnik | -1/+1 | |
| 2014-10-02 | Revert "Put slicing syntax behind a feature gate." | Aaron Turon | -1/+1 | |
| This reverts commit 95cfc35607ccf5f02f02de56a35a9ef50fa23a82. | ||||
| 2014-10-02 | docs: remove mentions of Gc. | Eduard Burtescu | -18/+2 | |
| 2014-10-02 | Put slicing syntax behind a feature gate. | Nick Cameron | -1/+1 | |
| [breaking-change] If you are using slicing syntax you will need to add #![feature(slicing_syntax)] to your crate. | ||||
| 2014-10-01 | Fix incorrect statement about ok() | Steve Klabnik | -5/+5 | |
| Fixes #17676. | ||||
| 2014-10-01 | Don't compare () to null. | Steve Klabnik | -8/+6 | |
| Fixes #17671. | ||||
| 2014-10-01 | use similar syntax in all arms | Steve Klabnik | -1/+1 | |
| Fixes #17672 | ||||
| 2014-10-01 | :fire: τ | Steve Klabnik | -6/+2 | |
| Fixes #17674 | ||||
| 2014-10-01 | Link plugins guide from elsewhere | Keegan McAllister | -6/+23 | |
| 2014-10-01 | Add a guide to compiler plugins | Keegan McAllister | -0/+261 | |
| Fixes #16983. | ||||
| 2014-10-01 | Add a red-box warning to the macros guide | Keegan McAllister | -0/+14 | |
| 2014-10-01 | Update some old references to rust.md | Keegan McAllister | -2/+2 | |
| 2014-10-01 | Use relative doc URLs in top-level guides | Keegan McAllister | -8/+8 | |
| 2014-10-01 | Add some notes about macro scoping | Keegan McAllister | -0/+60 | |
| 2014-10-01 | Guide: clarify exporting | Jiří Stránský | -3/+3 | |
| Mention that using `pub` is called exporting. Remove that `use` is called re-exporting, because `pub use` should be called re-exporting. The guide currently doesn't cover `pub use`. | ||||
| 2014-10-01 | rust.css: Make it more clear when code spans are links | Keegan McAllister | -0/+4 | |
| 2014-10-01 | Remove all use of librustuv | Aaron Turon | -1/+1 | |
| 2014-10-01 | auto merge of #17584 : pcwalton/rust/range-patterns-dotdotdot, r=nick29581 | bors | -5/+5 | |
| This breaks code that looks like: match foo { 1..3 => { ... } } Instead, write: match foo { 1...3 => { ... } } Closes #17295. r? @nick29581 | ||||
| 2014-09-30 | Add `if let` to the reference | Jakub Wieczorek | -1/+14 | |
| 2014-09-30 | Update based on PR feedback | Kevin Ballard | -2/+2 | |
| 2014-09-30 | Move `if let` behind a feature gate | Kevin Ballard | -1/+3 | |
| 2014-09-30 | librustc: Forbid `..` in range patterns. | Patrick Walton | -5/+5 | |
| This breaks code that looks like: match foo { 1..3 => { ... } } Instead, write: match foo { 1...3 => { ... } } Closes #17295. [breaking-change] | ||||
| 2014-09-29 | rollup merge of #17510 : MatejLach/find_fix | Alex Crichton | -2/+0 | |
| 2014-09-29 | auto merge of #17535 : Manishearth/rust/patch-2, r=steveklabnik | bors | -0/+1 | |
| It's a rather useful syntax, and non-obvious. A friend of mine is learning Rust and was trying to find a way to easily do such an initialization — he couldn't find it in the guide and was pretty surprised when I showed him. Looks like something that should be mentioned. r? @steveklabnik | ||||
| 2014-09-27 | auto merge of #17511 : MatejLach/rust/iter_guide_typo, r=alexcrichton | bors | -2/+2 | |
| The sentence "The new iterator `filter()` produces returns only the elements that that closure returned `true` for:" can be structured as: "The new iterator `filter()` produces only the elements that that closure returned `true` for:" or as: "The new iterator `filter()` returns only the elements that that closure returned `true` for:" however, not both. I went with "produces", since it then talks about returning true and having "return" so close together doesn't sound nice. r @steveklabnik ? | ||||
| 2014-09-27 | auto merge of #17512 : nodakai/rust/fix-ptr-guide, r=alexcrichton | bors | -0/+1 | |
| Fix rust-lang/rust#17255 This is such a trivial change. Devs: perhaps you might want to omit to run `make check` on Travis. | ||||
| 2014-09-27 | auto merge of #17506 : sfackler/rust/cfg-attr, r=alexcrichton | bors | -2/+2 | |
| cc #17490 Reopening of #16230 | ||||
| 2014-09-26 | Mention array sugar in guide | Manish Goregaokar | -0/+1 | |
 |
index : rust | |
| https://github.com/rust-lang/rust |
| summary refs log tree commit diff |