| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2018-01-30 | Run rustfmt on macro_parser.rs | Mark Mansi | -4/+6 | |
| 2018-01-30 | Run rustfmt on quoted.rs | Mark Mansi | -10/+21 | |
| 2018-01-30 | Update the macro parser to allow at most once repetitions for `?` Kleene | Mark Mansi | -16/+22 | |
| 2018-01-30 | Allow `?` as a KleeneOp in the macro parser | Mark Mansi | -46/+84 | |
| 2018-01-30 | The `static` keyword can now begin expressions | John Kåre Alsaker | -0/+1 | |
| 2018-01-30 | Auto merge of #47870 - kennytm:rollup, r=kennytm | bors | -165/+524 | |
| Rollup of 12 pull requests - Successful merges: #47515, #47603, #47718, #47732, #47760, #47780, #47822, #47826, #47836, #47839, #47853, #47855 - Failed merges: | ||||
| 2018-01-30 | Rollup merge of #47732 - mark-i-m:markim_comments_0001, r=jseyfried | kennytm | -126/+351 | |
| Run rustfmt and add doc comments to libsyntax/ext/tt/macro_parser.rs Similar to #47603 cc @theotherphil since you reviewed my other PR :smile: And because they are already assigned on #47603: r? @arielb1 | ||||
| 2018-01-30 | Rollup merge of #47603 - mark-i-m:markim_comments_0000, r=jseyfried | kennytm | -39/+173 | |
| Run rustfmt and add doc comments to libsyntax/ext/tt/quoted.rs I was already going to try to understand this code to try to implement rust-lang/rfcs#2298. I figured I would put that knowledge into comments and share... This PR contains _no changes_ to the code itself -- just formatting and comments. I'm not sure what the best way to do this is. I plan to make more such PR for other files, but I figured it would have fewer conflicts if I do it file by file... | ||||
| 2018-01-30 | Auto merge of #45294 - petrochenkov:prioplus, r=nikomatsakis | bors | -10/+25 | |
| syntax: Lower priority of `+` in `impl Trait`/`dyn Trait` Now you have to write `Fn() -> (impl A + B)` instead of `Fn() -> impl A + B`, this is consistent with priority of `+` in trait objects (`Fn() -> A + B` means `(Fn() -> A) + B`). To make this viable I changed the syntax to also permit `+` in return types in function declarations ``` fn f() -> dyn A + B { ... } // OK, don't have to write `-> (dyn A + B)` // This is acceptable, because `dyn A + B` here is an isolated type and // not part of a larger type with various operator priorities in play // like `dyn A + B` in `Fn() -> dyn A + B` despite syntax similarities. ``` but you still have to use `-> (dyn A + B)` in function types and function-like trait object types (see this PR's tests for examples). This can be a breaking change for code using `impl Trait` on nightly. The thing that is most likely to break is `&impl A + B`, it needs to be rewritten as `&(impl A + B)`. cc https://github.com/rust-lang/rust/issues/34511 https://github.com/rust-lang/rust/issues/44662 https://github.com/rust-lang/rfcs/pull/438 | ||||
| 2018-01-29 | fix typos | Mark Mansi | -4/+4 | |
| 2018-01-29 | Update comment | Mark Mansi | -1/+2 | |
| 2018-01-29 | Toggle span highlighting on `-Zteach` | Esteban Küber | -1/+3 | |
| 2018-01-29 | Add internal-only rustc_serialize_exclude_null attribute for making the ↵ | Manish Goregaokar | -0/+8 | |
| field only exist in the json if the flag is passed | ||||
| 2018-01-29 | Add -Zapproximate-suggestions | Manish Goregaokar | -4/+18 | |
| 2018-01-29 | Add approximate suggestions for rustfix | Manish Goregaokar | -7/+11 | |
| This adds `span_approximate_suggestion()` that lets you emit a suggestion marked as "approximate" in the JSON output. UI users see no difference. This is for when rustc and clippy wish to emit suggestions which will make sense to the reader (e.g. they may have placeholders like `<type>`) but are not source-applicable, so that rustfix/etc can ignore these. fixes #39254 | ||||
| 2018-01-28 | Auto merge of #47800 - Pulkit07:issue47755, r=sfackler | bors | -3/+1 | |
| don't mention tasks in stability warnings of #[thread_local] #47755 This is a fix for issue #47755. | ||||
| 2018-01-28 | Auto merge of #47767 - estebank:as-suggestion, r=petrochenkov | bors | -0/+1 | |
| Correctly format `extern crate` conflict resolution help Closes #45799. Follow up to @Cldfire's #45820. If the `extern` statement that will have a suggestion ends on a `;`, synthesize a new span that doesn't include it. | ||||
| 2018-01-27 | Make `+` in `impl/dyn Trait` non-associative | Vadim Petrochenkov | -3/+19 | |
| 2018-01-27 | syntax: Permit `+` in return types of function declarations | Vadim Petrochenkov | -6/+6 | |
| `+` is still disallowed in function types and function-like traits | ||||
| 2018-01-27 | syntax: Lower priority of `+` in `impl Trait`/`dyn Trait` | Vadim Petrochenkov | -4/+3 | |
| 2018-01-27 | Fixed infinite loop issues and added some improved logging. | David Wood | -6/+20 | |
| 2018-01-27 | Now handling case where span has same lo and hi. | David Wood | -1/+6 | |
| 2018-01-27 | next_point now handles creating spans over multibyte characters. | David Wood | -5/+9 | |
| 2018-01-27 | Replaced multi-byte character handling in end_point with potentially more ↵ | David Wood | -23/+59 | |
| performant variant. | ||||
| 2018-01-27 | end_point handling multibyte characters correctly. | David Wood | -3/+42 | |
| 2018-01-27 | don't mention tasks in stability warnings of #[thread_local] #47755 | Pulkit Goyal | -3/+1 | |
| This is a fix for issue #47755. | ||||
| 2018-01-26 | Instead of modifying the item's span synthesize it | Esteban Küber | -2/+1 | |
| 2018-01-26 | review comment | Esteban Küber | -6/+4 | |
| 2018-01-26 | Consider all whitespace when preparing span | Esteban Küber | -2/+26 | |
| 2018-01-26 | A few more comments | Mark Mansi | -0/+8 | |
| 2018-01-26 | Still more comments | Mark Mansi | -2/+26 | |
| 2018-01-26 | Added/improved comments | Mark Mansi | -17/+61 | |
| 2018-01-26 | Added lots of comments + minor reorganization | Mark Mansi | -34/+94 | |
| 2018-01-26 | Added a bunch of comments to macro_parser.rs | Mark Mansi | -10/+62 | |
| 2018-01-26 | Run rustfmt on /libsyntax/ext/tt/macro_parser.rs | Mark Mansi | -78/+114 | |
| 2018-01-26 | Merge branch 'no-stderr-sink' of https://github.com/Zoxc/rust into rollup | Alex Crichton | -50/+50 | |
| 2018-01-25 | Correctly format `extern crate` conflict resolution help | Cldfire | -1/+3 | |
| 2018-01-26 | Do not capture stderr in the compiler. Instead just panic silently for fatal ↵ | John Kåre Alsaker | -50/+50 | |
| errors | ||||
| 2018-01-25 | Rollup merge of #47502 - petrochenkov:label, r=eddyb | Alex Crichton | -117/+108 | |
| AST/HIR: Add a separate structure for labels | ||||
| 2018-01-25 | Auto merge of #47006 - bitshifter:stabilize-repr-align, r=eddyb | bors | -13/+17 | |
| Stabilized `#[repr(align(x))]` attribute (RFC 1358) Stabilzed `#[repr(align(x))]` with attr_literal syntax as proposed by @eddyb https://github.com/rust-lang/rust/issues/33626#issuecomment-348467804 | ||||
| 2018-01-23 | Adds support for immovable generators. Move checking of invalid borrows ↵ | John Kåre Alsaker | -15/+62 | |
| across suspension points to borrowck. Fixes #44197, #45259 and #45093. | ||||
| 2018-01-23 | Stabilized `#[repr(align(x))]` attribute (RFC 1358) | Cameron Hart | -13/+17 | |
| 2018-01-22 | AST/HIR: Add a separate structure for labels | Vadim Petrochenkov | -117/+108 | |
| 2018-01-22 | Auto merge of #47158 - rkruppe:repr-transparent, r=eddyb | bors | -1/+12 | |
| Implement repr(transparent) r? @eddyb for the functional changes. The bulk of the PR is error messages and docs, might be good to have a doc person look over those. cc #43036 cc @nox | ||||
| 2018-01-21 | Rollup merge of #47247 - estebank:suggest-cast, r=petrochenkov | Guillaume Gomez | -59/+171 | |
| Suggest casting on numeric type error Re #47168. | ||||
| 2018-01-21 | Fix typos | Mark Mansi | -3/+3 | |
| 2018-01-19 | Add a bunch of doc comments | Mark Mansi | -3/+72 | |
| 2018-01-19 | Run rustfmt and add comments | Mark Mansi | -38/+103 | |
| 2018-01-18 | Rollup merge of #47481 - estebank:unused-args, r=arielb1 | kennytm | -29/+34 | |
| Point at unused arguments for format string Avoid overlapping spans by only pointing at the arguments that are not being used in the argument string. Enable libsyntax to have diagnostics with multiple primary spans by accepting `Into<MultiSpan>` instead of `Span`. Partially addresses #41850. | ||||
| 2018-01-16 | Implement repr(transparent) | Robin Kruppe | -1/+12 | |
