711 Commits

Author	SHA1	Message	Date
Matthias Krüger	40dddd3305	use matches!() macro for simple if let conditions	2020-09-18 20:28:35 +02:00
Aaron Hill	156ef2bee8	Attach tokens to ast::Stmt ... We currently only attach tokens when parsing a `:stmt` matcher for a `macro_rules!` macro. Proc-macro attributes on statements are still unstable, and need additional work.	2020-09-10 17:33:06 -04:00
Aaron Hill	c1011165e6	Attach TokenStream to ast::Visibility ... A `Visibility` does not have outer attributes, so we only capture tokens when parsing a `macro_rules!` matcher	2020-09-10 17:33:06 -04:00
Aaron Hill	3815e91ccd	Attach tokens to NtMeta (ast::AttrItem) ... An `AttrItem` does not have outer attributes, so we only capture tokens when parsing a `macro_rules!` matcher	2020-09-10 17:33:06 -04:00
Aaron Hill	1823dea7df	Attach TokenStream to ast::Ty ... A `Ty` does not have outer attributes, so we only capture tokens when parsing a `macro_rules!` matcher	2020-09-10 17:33:05 -04:00
Aaron Hill	de4bd9f0f8	Attach TokenStream to ast::Block ... A `Block` does not have outer attributes, so we only capture tokens when parsing a `macro_rules!` matcher	2020-09-10 17:33:05 -04:00
Matthias Krüger	9bb10cc907	use push(char) instead of push_str(&str) to add single chars to strings ... clippy::single-char-push-str	2020-09-10 13:58:41 +02:00
Esteban Küber	2ac89ff994	Point at named argument not found when using format_args_capture instead of whole format string	2020-09-08 10:10:45 -07:00
Sasha	3524c3ef43	Improve recovery on malformed format call ... If a comma in a format call is replaced with a similar token, then we emit an error and continue parsing, instead of stopping at this point.	2020-09-02 13:18:19 +02:00
Sasha	f6d18db402	Use string literal directly when available in format ... Previous implementation used the `Parser::parse_expr` function in order to extract the format expression. If the first comma following the format expression was mistakenly replaced with a dot, then the next format expression was eaten by the function, because it looked as a syntactically valid expression, which resulted in incorrectly spanned error messages. The way the format expression is exctracted is changed: we first look at the first available token in the first argument supplied to the `format!` macro call. If it is a string literal, then it is promoted as a format expression immediatly, otherwise we fall back to the original `parse_expr`-related method. This allows us to ensure that the parser won't consume too much tokens when a typo is made. A test has been created so that it is ensured that the issue is properly fixed.	2020-08-30 22:09:58 +02:00
mark	9e5f7d5631	mv compiler to compiler/	2020-08-30 18:45:07 +03:00