rust/src/libsyntax/parse/parser.rs, branch tryhttps://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=try2019-11-07T12:50:12+00:00move parse/parser.rs -> parse/parser/mod.rs2019-11-07T12:50:12+00:00Mazdak Farrokhzadtwingoow@gmail.com2019-10-25T02:57:40+00:00urn:sha1:da116223c709392db3741d966cb49ea0407de19eRollup merge of #65974 - Centril:matcher-friendly-gating, r=petrochenkov2019-11-07T07:51:57+00:00Mazdak Farrokhzadtwingoow@gmail.com2019-11-07T07:51:57+00:00urn:sha1:e19cb40fda70ea3f75bc1927c114ea53d231b288
A scheme for more macro-matcher friendly pre-expansion gating
Pre-expansion gating will now avoid gating macro matchers that did not result in `Success(...)`. That is, the following is now OK despite `box 42` being a valid `expr` and that form being pre-expansion gated:
```rust
macro_rules! m {
($e:expr) => { 0 }; // This fails on the input below due to `, foo`.
(box $e:expr, foo) => { 1 }; // Successful matcher, we should get `2`.
}
fn main() {
assert_eq!(1, m!(box 42, foo));
}
```
Closes https://github.com/rust-lang/rust/issues/65846.
r? @petrochenkov
cc @Mark-Simulacrum
parser: allow ABIs from literal macro fragments2019-11-07T04:25:31+00:00Mazdak Farrokhzadtwingoow@gmail.com2019-10-27T23:29:23+00:00urn:sha1:1db4d607e7621a7d813743e83125859a47970f79parser: don't hardcode ABIs into grammar2019-11-07T04:25:31+00:00Mazdak Farrokhzadtwingoow@gmail.com2019-10-27T22:14:35+00:00urn:sha1:beddf67a4b1ce5f1e14a67690644690c4b1bcfaarevamp pre-expansion gating infra2019-11-06T11:30:08+00:00Mazdak Farrokhzadtwingoow@gmail.com2019-10-30T15:38:16+00:00urn:sha1:fe95cd2f4b3a722e023dc7bba8ff65136be441caRollup merge of #66054 - petrochenkov:delspan, r=estebank2019-11-06T02:28:09+00:00Mazdak Farrokhzadtwingoow@gmail.com2019-11-06T02:28:09+00:00urn:sha1:e5da1a12e745e0d92cfae421673faac4fd5e4069
syntax: Avoid span arithmetic for delimiter tokens
The +/-1 logic is from the time where the whole group had a single span and the delimiter spans had to be calculated from it.
Now the delimiters have their own spans which are constructed by lexer or proc macro API and can be used directly.
If those spans are not perfect, then it should be fixed by tweaking the corresponding lexer logic rather than by trying to add or substract `1` from the span boundaries.
Fixes https://github.com/rust-lang/rust/issues/62524
r? @estebank
syntax: Avoid span arithmetics for delimiter tokens2019-11-03T11:58:12+00:00Vadim Petrochenkovvadim.petrochenkov@gmail.com2019-11-03T11:58:01+00:00urn:sha1:90f891d8ae9073623769fac18f00c4f1031fcb59Do not complain about missing `fn main()` in some cases2019-10-30T19:05:26+00:00Esteban Küberesteban@kuber.com.ar2019-10-29T00:44:20+00:00urn:sha1:454e2aa8c99850c9393fb2314e1a71da08120063Reduce ammount of errors given unclosed delimiter2019-10-30T19:05:17+00:00Esteban Küberesteban@kuber.com.ar2019-10-26T01:30:02+00:00urn:sha1:053a09529a41931a217daecbe879b88386101249
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.
Rollup merge of #65790 - Centril:move-report-invalid, r=davidtwco2019-10-25T11:12:55+00:00Mazdak Farrokhzadtwingoow@gmail.com2019-10-25T11:12:55+00:00urn:sha1:c0bbb4bcdce880711c13b535fc4d9cd369741782
move report_invalid_macro_expansion_item to item.rs
From https://github.com/rust-lang/rust/pull/65324.
r? @Mark-Simulacrum