| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2019-11-06 | Rollup merge of #66139 - euclio:pluralize, r=nagisa | Mazdak Farrokhzad | -8/+8 | |
| use American spelling for `pluralize!` | ||||
| 2019-11-06 | Rollup merge of #65776 - nnethercote:rename-LocalInternedString-and-more, ↵ | Mazdak Farrokhzad | -5/+5 | |
| r=estebank Rename `LocalInternedString` and more This PR renames `LocalInternedString` as `SymbolStr`, removes an unnecessary `impl` from it, improves comments, and cleans up some `SymbolStr` uses. r? @estebank | ||||
| 2019-11-06 | Rollup merge of #66098 - estebank:path-asciption-typo, r=Centril | Mazdak Farrokhzad | -4/+12 | |
| Detect `::` -> `:` typo when involving turbofish Fix #65569. | ||||
| 2019-11-05 | use American spelling for `pluralize!` | Andy Russell | -8/+8 | |
| 2019-11-05 | Account for typo in turbofish and suggest `::` | Esteban Küber | -4/+10 | |
| 2019-11-04 | Detect `::` -> `:` typo when involving turbofish | Esteban Küber | -1/+3 | |
| 2019-11-04 | Auto merge of #65838 - estebank:resilient-recovery, r=Centril | bors | -15/+52 | |
| Reduce amount of errors given unclosed delimiter When in a file with a non-terminated item, catch the error and consume the block instead of trying to recover it on a more granular way in order to reduce the amount of unrelated errors that would be fixed after adding the missing closing brace. Also point out the possible location of the missing closing brace. Fix #63690. | ||||
| 2019-11-02 | Remove the `AsRef` impl for `SymbolStr`. | Nicholas Nethercote | -4/+4 | |
| Because it's highly magical, which goes against the goal of keeping `SymbolStr` simple. Plus it's only used in a handful of places that only require minor changes. | ||||
| 2019-11-02 | Simplify various `Symbol` use points. | Nicholas Nethercote | -1/+1 | |
| Including removing a bunch of unnecessary `.as_str()` calls, and a bunch of unnecessary sigils. | ||||
| 2019-10-31 | Create new error E0743 | Guillaume Gomez | -2/+5 | |
| 2019-10-30 | Do not complain about missing `fn main()` in some cases | Esteban Küber | -0/+5 | |
| 2019-10-30 | Reduce ammount of errors given unclosed delimiter | Esteban Küber | -15/+47 | |
| When in a file with a non-terminated item, catch the error and consume the block instead of trying to recover it more granularly in order to reduce the amount of unrelated errors that would be fixed after adding the missing closing brace. Also point out the possible location of the missing closing brace. | ||||
| 2019-10-28 | review comments | Esteban Küber | -42/+39 | |
| 2019-10-28 | Tweak unexpected token wording | Esteban Küber | -5/+5 | |
| 2019-10-28 | Use heuristics to recover parsing of missing `;` | Esteban Küber | -51/+70 | |
| - Detect `,` and `:` typos where `;` was intended. - When the next token could have been the start of a new statement, detect a missing semicolon. | ||||
| 2019-10-28 | Rollup merge of #65792 - Centril:split-syntax-2, r=petrochenkov | Mazdak Farrokhzad | -1/+1 | |
| rustc, rustc_passes: reduce deps on rustc_expand Part of #65324. r? @petrochenkov | ||||
| 2019-10-27 | syntax/attr: reduce reliance on parser | Mazdak Farrokhzad | -1/+1 | |
| 2019-10-26 | review comments and tweaks | Esteban Küber | -1/+1 | |
| 2019-10-25 | Rollup merge of #65790 - Centril:move-report-invalid, r=davidtwco | Mazdak Farrokhzad | -0/+20 | |
| move report_invalid_macro_expansion_item to item.rs From https://github.com/rust-lang/rust/pull/65324. r? @Mark-Simulacrum | ||||
| 2019-10-25 | move report_invalid_macro_expansion_item to item.rs | Mazdak Farrokhzad | -0/+20 | |
| 2019-10-24 | pre-expansion gate type_ascription | Mazdak Farrokhzad | -0/+1 | |
| 2019-10-24 | pre-expansion gate box_syntax | Mazdak Farrokhzad | -1/+3 | |
| 2019-10-24 | pre-expansion gate label_break_value | Mazdak Farrokhzad | -0/+4 | |
| 2019-10-24 | pre-expansion gate try_blocks | Mazdak Farrokhzad | -1/+3 | |
| 2019-10-24 | pre-expansion gate exclusive_range_pattern | Mazdak Farrokhzad | -2/+7 | |
| 2019-10-24 | pre-expansion gate box_patterns | Mazdak Farrokhzad | -1/+3 | |
| 2019-10-24 | pre-expansion gate decl_macro | Mazdak Farrokhzad | -0/+5 | |
| 2019-10-24 | pre-expansion gate const_generics | Mazdak Farrokhzad | -0/+4 | |
| 2019-10-24 | pre-expansion gate associated_type_bounds | Mazdak Farrokhzad | -2/+10 | |
| 2019-10-24 | pre-expansion gate trait_alias. | Mazdak Farrokhzad | -0/+2 | |
| 2019-10-24 | syntax: reject `trait Foo: Bar = Baz;`. | Mazdak Farrokhzad | -8/+20 | |
| Add test for rejecting `trait A: B1 = B2;`. Also test rejection of `trait A: = B;`. | ||||
| 2019-10-23 | Rollup merge of #65686 - yjhmelody:yjhmelody-patch-1, r=Centril | Yuki Okushi | -2/+8 | |
| refactor and move `maybe_append` | ||||
| 2019-10-22 | refactor maybe_append | yjhmelody | -2/+8 | |
| 2019-10-18 | Rollup merge of #65552 - JohnTitor:use-bitwise-not, r=Dylan-DPC | Tyler Mandry | -1/+1 | |
| Clarify diagnostics when using `~` as a unary op It seems we prefer `bitwise not` to `bitwise negation`. Fixes #57239 r? @estebank | ||||
| 2019-10-18 | Clarify diagnostics when using `~` as a unary op | Yuki Okushi | -1/+1 | |
| 2019-10-18 | Change `Lit::tokens()` to `Lit::token_tree()`. | Nicholas Nethercote | -5/+4 | |
| Because most of the call sites have an easier time working with a `TokenTree` instead of a `TokenStream`. | ||||
| 2019-10-16 | ui-fulldeps: make them pass again? | Mazdak Farrokhzad | -2/+2 | |
| 2019-10-16 | make tidy happy | Mazdak Farrokhzad | -3/+13 | |
| 2019-10-16 | parser: leave a FIXME for later | Mazdak Farrokhzad | -0/+2 | |
| 2019-10-16 | move SeqSep to parser.rs | Mazdak Farrokhzad | -4/+5 | |
| 2019-10-16 | move syntax::ext to new crate syntax_expand | Mazdak Farrokhzad | -15/+15 | |
| 2019-10-16 | syntax::parse: don't depend on syntax::ext | Mazdak Farrokhzad | -6/+12 | |
| 2019-10-16 | syntax: reduce visibilities | Mazdak Farrokhzad | -65/+67 | |
| 2019-10-16 | move diagnostics.rs into parser/ | Mazdak Farrokhzad | -4/+1488 | |
| 2019-10-16 | syntax: extract parse_cfg_attr | Mazdak Farrokhzad | -0/+21 | |
| 2019-10-16 | syntax: extract parse_derive_paths | Mazdak Farrokhzad | -1/+16 | |
| 2019-10-16 | move parse::attr -> parse::parser::attr | Mazdak Farrokhzad | -0/+330 | |
| 2019-10-15 | move parse_lit to expr.rs | Mazdak Farrokhzad | -6/+166 | |
| 2019-10-14 | Rollup merge of #65410 - Centril:intersection-pat-recover, r=davidtwco,varkor | Tyler Mandry | -0/+60 | |
| syntax: add parser recovery for intersection- / and-patterns `p1 @ p2` Fixes https://github.com/rust-lang/rust/issues/65400. The recovery comes in two flavors: 1. We know that `p2` is a binding so we can invert as `p2 @ p1`: ```rust error: pattern on wrong side of `@` --> $DIR/intersection-patterns.rs:13:9 | LL | Some(x) @ y => {} | -------^^^- | | | | | binding on the right, should be to the left | pattern on the left, should be to the right | help: switch the order: `y @ Some(x)` ``` 2. Otherwise we emit a generic diagnostic for the lack of support for intersection patterns: ```rust error: left-hand side of `@` must be a binding --> $DIR/intersection-patterns.rs:23:9 | LL | Some(x) @ Some(y) => {} | -------^^^------- | | | | | also a pattern | interpreted as a pattern, not a binding | = note: bindings are `x`, `mut x`, `ref x`, and `ref mut x` ``` For more on and-patterns, see e.g. https://docs.microsoft.com/en-us/dotnet/fsharp/language-reference/pattern-matching#and-pattern. r? @davidtwco cc @varkor @lzutao | ||||
| 2019-10-14 | recover_intersection_pat: adjust wording | Mazdak Farrokhzad | -3/+3 | |
