rust/src/libsyntax/parse/parser/item.rs, branch tryhttps://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=try2019-11-10T02:57:18+00:00move syntax::parse -> librustc_parse2019-11-10T02:57:18+00:00Mazdak Farrokhzadtwingoow@gmail.com2019-10-15T20:48:13+00:00urn:sha1:4ae2728fa8052915414127dce28245eb8f70842a
also move MACRO_ARGUMENTS -> librustc_parse
ast::ItemKind::Fn: use ast::FnSig2019-11-08T08:32:20+00:00Mazdak Farrokhzadtwingoow@gmail.com2019-11-07T12:33:37+00:00urn:sha1:b4c6abcf9e6c1d2710e7ad6a9ce44b3ca6b10d52ast::MethodSig -> ast::FnSig2019-11-08T08:32:20+00:00Mazdak Farrokhzadtwingoow@gmail.com2019-11-07T12:11:59+00:00urn:sha1:2cd48e8a3b71256d7db1ac61e8994c06620238b6move PResult to librustc_errors2019-11-07T12:58:36+00:00Mazdak Farrokhzadtwingoow@gmail.com2019-10-11T11:06:36+00:00urn:sha1:3667e6248ec18740ce57db7997333a30c991929bRollup 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:beddf67a4b1ce5f1e14a67690644690c4b1bcfaaMake doc comments cheaper with `AttrKind`.2019-11-06T12:05:07+00:00Nicholas Nethercotennethercote@mozilla.com2019-10-23T19:33:12+00:00urn:sha1:eea6f23a0ed67fd8c6b8e1b02cda3628fee56b2f
`AttrKind` is a new type with two variants, `Normal` and `DocComment`. It's a
big performance win (over 10% in some cases) because `DocComment` lets doc
comments (which are common) be represented very cheaply.
`Attribute` gets some new helper methods to ease the transition:
- `has_name()`: check if the attribute name matches a single `Symbol`; for
`DocComment` variants it succeeds if the symbol is `sym::doc`.
- `is_doc_comment()`: check if it has a `DocComment` kind.
- `{get,unwrap}_normal_item()`: extract the item from a `Normal` variant;
panic otherwise.
Fixes #60935.
revamp pre-expansion gating infra2019-11-06T11:30:08+00:00Mazdak Farrokhzadtwingoow@gmail.com2019-10-30T15:38:16+00:00urn:sha1:fe95cd2f4b3a722e023dc7bba8ff65136be441caReduce 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.