| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2024-06-06 | Revert "Rollup merge of #124099 - voidc:disallow-ambiguous-expr-attrs, ↵ | Rémy Rakic | -76/+0 | |
| r=davidtwco" This reverts commit 57dad1d75e562ff73051c1c43b07eaf65c7dbd74, reversing changes made to 36316df9fe6c3e246153fe6e78967643cf08c148. | ||||
| 2024-05-10 | Fix parse error message for meta items | León Orell Valerian Liehr | -30/+51 | |
| 2024-05-04 | compiletest: add enable-by-default check-cfg | Urgau | -2/+6 | |
| 2024-04-18 | Disallow ambiguous attributes on expressions | Dominik Stolz | -0/+76 | |
| 2024-04-07 | Unify all the always-false cfgs under the `FALSE` cfg | Urgau | -9/+9 | |
| 2024-03-21 | Rewrite `parse_meta_item`. | Nicholas Nethercote | -0/+37 | |
| It can't use `maybe_whole`, but it can match `maybe_whole` more closely. Also add a test for a case that wasn't previously covered. | ||||
| 2024-02-26 | Properly emit `expected ;` on `#[attr] expr` | Lieselotte | -2/+43 | |
| 2024-02-16 | [AUTO-GENERATED] Migrate ui tests from `//` to `//@` directives | 许杰友 Jieyou Xu (Joe) | -6/+6 | |
| 2024-01-26 | Properly recover from trailing attr in body | Esteban Küber | -0/+36 | |
| When encountering an attribute in a body, we try to recover from an attribute on an expression (as opposed to a statement). We need to properly clean up when the attribute is at the end of the body where a tail expression would be. Fix #118164. | ||||
| 2024-01-12 | Suggest quoting unquoted idents in attrs | sjwang05 | -0/+54 | |
| 2023-12-28 | Don't expect bodyless arms if the pattern can never be a never pattern | Lieselotte | -9/+9 | |
| 2023-12-03 | Parse a pattern with no arm | Nadrieril | -9/+9 | |
| 2023-11-24 | Show number in error message even for one error | Nilstrieb | -10/+10 | |
| Co-authored-by: Adrian <adrian.iosdev@gmail.com> | ||||
| 2023-11-16 | Handle attempts to have multiple `cfg`d tail expressions | Esteban Küber | -0/+73 | |
| When encountering code that seems like it might be trying to have multiple tail expressions depending on `cfg` information, suggest alternatives that will success to parse. ```rust fn foo() -> String { #[cfg(feature = "validation")] [1, 2, 3].iter().map(|c| c.to_string()).collect::<String>() #[cfg(not(feature = "validation"))] String::new() } ``` ``` error: expected `;`, found `#` --> $DIR/multiple-tail-expr-behind-cfg.rs:5:64 | LL | #[cfg(feature = "validation")] | ------------------------------ only `;` terminated statements or tail expressions are allowed after this attribute LL | [1, 2, 3].iter().map(|c| c.to_string()).collect::<String>() | ^ expected `;` here LL | #[cfg(not(feature = "validation"))] | - unexpected token | help: add `;` here | LL | [1, 2, 3].iter().map(|c| c.to_string()).collect::<String>(); | + help: alternatively, consider surrounding the expression with a block | LL | { [1, 2, 3].iter().map(|c| c.to_string()).collect::<String>() } | + + help: it seems like you are trying to provide different expressions depending on `cfg`, consider using `if cfg!(..)` | LL ~ if cfg!(feature = "validation") { LL ~ [1, 2, 3].iter().map(|c| c.to_string()).collect::<String>() LL ~ } else if cfg!(not(feature = "validation")) { LL ~ String::new() LL + } | ``` Fix #106020. | ||||
| 2023-10-09 | Move some tests around | Esteban Küber | -0/+696 | |
