rust/src/libsyntax/parse, branch 1.10.0

syntax: Refactor parsing of method declarations

2016-05-14T10:23:37+00:00

Fix spans and expected token lists, fix #33413 + other cosmetic improvements Add test for #33413 Convert between `Arg` and `ExplicitSelf` precisely Simplify pretty-printing for methods

Rollup merge of #33336 - birkenfeld:issue-27361, r=sfackler

2016-05-07T19:35:17+00:00

parser: do not try to continue with `unsafe` on foreign fns The changed line makes it look like `unsafe` is allowed, but the first statement of `parse_item_foreign_fn` is: ``` self.expect_keyword(keywords::Fn)?; ``` So we get the strange "expected one of `fn`, `pub`, `static`, or `unsafe`, found `unsafe`". Fixes: #27361

Auto merge of #33333 - birkenfeld:issue-30318, r=Manishearth

2016-05-07T10:01:44+00:00

parser: show a helpful note on unexpected inner comment Fixes: #30318.

Auto merge of #33311 - birkenfeld:issue33262, r=nrc

2016-05-07T05:39:43+00:00

parser: fix suppression of syntax errors in range RHS Invalid expressions on the RHS were just swallowed without generating an error. The new version more closely mirrors the code for parsing `..x` in the `parse_prefix_range_expr` method below, where no cancel is done either. Fixes #33262.

Auto merge of #33128 - xen0n:more-confusing-unicode-chars, r=nagisa

2016-05-05T15:50:23+00:00

Add more aliases for Unicode confusable chars Building upon #29837, this PR: * added aliases for space characters, * distinguished square brackets from parens, and * added common CJK punctuation characters as aliases. This will especially help CJK users who may have forgotten to switch off IME when coding.

parser: show a helpful note on unexpected inner comment

2016-05-03T15:53:23+00:00

Fixes: #30318.

Rollup merge of #33343 - birkenfeld:issue-32214, r=Manishearth

2016-05-03T14:24:55+00:00

parser: change warning into an error on `T` part of #32214 This seems to be the obvious fix, and the error message is consistent with all the other parser errors ("expected x, found y").

Rollup merge of #33334 - birkenfeld:issue29088, r=Manishearth

2016-05-03T02:35:29+00:00

lexer: do not display char confusingly in error message Current code leads to messages like `... use a \xHH escape: \u{e4}` which is confusing. The printed span already points to the offending character, which should be enough to identify the non-ASCII problem. Fixes: #29088

replace fileline_{help,note} with {help,note}

2016-05-02T15:49:23+00:00

The extra filename and line was mainly there to keep the indentation relative to the main snippet; now that this doesn't include filename/line-number as a prefix, it is distracted.

parser: change warning into an error on `T`

2016-05-02T13:10:28+00:00

Fixes: #32214