rust/tests/ui/consts/issue-90878-2.stderr

error: unexpected expression: `|x| [b; x]`
  --> $DIR/issue-90878-2.rs:1:7
   |
LL |  #![l=|x|[b;x ]]
   |       ^^^^^^^^^

error: cannot find attribute `l` in this scope
  --> $DIR/issue-90878-2.rs:1:5
   |
LL |  #![l=|x|[b;x ]]
   |     ^

error: aborting due to 2 previous errors
Overhaul `MacArgs::Eq`. The value in `MacArgs::Eq` is currently represented as a `Token`. Because of `TokenKind::Interpolated`, `Token` can be either a token or an arbitrary AST fragment. In practice, a `MacArgs::Eq` starts out as a literal or macro call AST fragment, and then is later lowered to a literal token. But this is very non-obvious. `Token` is a much more general type than what is needed. This commit restricts things, by introducing a new type `MacArgsEqKind` that is either an AST expression (pre-lowering) or an AST literal (post-lowering). The downside is that the code is a bit more verbose in a few places. The benefit is that makes it much clearer what the possibilities are (though also shorter in some other places). Also, it removes one use of `TokenKind::Interpolated`, taking us a step closer to removing that variant, which will let us make `Token` impl `Copy` and remove many "handle Interpolated" code paths in the parser. Things to note: - Error messages have improved. Messages like this: ``` unexpected token: `"bug" + "found"` ``` now say "unexpected expression", which makes more sense. Although arbitrary expressions can exist within tokens thanks to `TokenKind::Interpolated`, that's not obvious to anyone who doesn't know compiler internals. - In `parse_mac_args_common`, we no longer need to collect tokens for the value expression. 2022-04-28 20:52:01 +00:00			error: unexpected expression: `\|x\| [b; x]`
Fix `non-constant value` ICE (#90878) This also fixes the same suggestion, which was kind of broken, because it just searched for the last occurence of `const` to replace with a `let`. This works great in some cases, but when there is no const and a leading space to the file, it doesn't work and panic with overflow because it thought that it had found a const. I also changed the suggestion to only trigger if the `const` and the non-constant value are on the same line, because if they aren't, the suggestion is very likely to be wrong. Also don't trigger the suggestion if the found `const` is on line 0, because that triggers the ICE. 2021-11-15 19:40:29 +00:00			`--> $DIR/issue-90878-2.rs:1:7`
			`\|`
			`LL \| #![l=\|x\|[b;x ]]`
			`\| ^^^^^^^^^`

			error: cannot find attribute `l` in this scope
			`--> $DIR/issue-90878-2.rs:1:5`
			`\|`
			`LL \| #![l=\|x\|[b;x ]]`
			`\| ^`

Do not visit attributes in `LateResolutionVisitor`. 2021-11-24 22:07:13 +00:00			`error: aborting due to 2 previous errors`
Fix `non-constant value` ICE (#90878) This also fixes the same suggestion, which was kind of broken, because it just searched for the last occurence of `const` to replace with a `let`. This works great in some cases, but when there is no const and a leading space to the file, it doesn't work and panic with overflow because it thought that it had found a const. I also changed the suggestion to only trigger if the `const` and the non-constant value are on the same line, because if they aren't, the suggestion is very likely to be wrong. Also don't trigger the suggestion if the found `const` is on line 0, because that triggers the ICE. 2021-11-15 19:40:29 +00:00