macro_literal_matcher: fixes per petrochenkov's review

This commit is contained in:
Dan Aloni 2018-11-20 09:11:12 +02:00
parent fc284c1eee
commit b8ae7b801b
3 changed files with 3 additions and 5 deletions

View file

@ -1033,9 +1033,9 @@ fn is_legal_fragment_specifier(_sess: &ParseSess,
frag_name: &str, frag_name: &str,
_frag_span: Span) -> bool { _frag_span: Span) -> bool {
/* /*
* If new fragmnet specifiers are invented in nightly, `_sess`, * If new fragment specifiers are invented in nightly, `_sess`,
* `_features`, `_attrs`, and `_frag_span` will be useful for * `_features`, `_attrs`, and `_frag_span` will be useful here
* here for checking against feature gates. See past versions of * for checking against feature gates. See past versions of
* this function. * this function.
*/ */
match frag_name { match frag_name {

View file

@ -9,7 +9,6 @@
// except according to those terms. // except according to those terms.
// run-pass // run-pass
#![cfg_attr(stage0, feature(macro_literal_matcher))]
macro_rules! a { macro_rules! a {
($i:literal) => { "right" }; ($i:literal) => { "right" };

View file

@ -9,7 +9,6 @@
// except according to those terms. // except according to those terms.
// run-pass // run-pass
#![cfg_attr(stage0, feature(macro_literal_matcher))]
macro_rules! mtester { macro_rules! mtester {
($l:literal) => { ($l:literal) => {