rust/tests/ui/macros/issue-42954.stderr

error: `<` is interpreted as a start of generic arguments for `u32`, not a comparison
  --> $DIR/issue-42954.rs:7:19
   |
LL |         $i as u32 < 0
   |                   ^ - interpreted as generic arguments
   |                   |
   |                   not interpreted as comparison
...
LL |     is_plainly_printable!(c);
   |     ------------------------ in this macro invocation
   |
   = note: this error originates in the macro `is_plainly_printable` (in Nightly builds, run with -Z macro-backtrace for more info)
help: try comparing the cast value
   |
LL |         ($i as u32) < 0
   |         +         +

error: aborting due to previous error
Fix spans for binary operator expression with interpolated identifiers 2017-07-04 09:04:34 -05:00			error: `<` is interpreted as a start of generic arguments for `u32`, not a comparison
Remove licenses 2018-12-25 09:56:47 -06:00			`--> $DIR/issue-42954.rs:7:19`
Fix spans for binary operator expression with interpolated identifiers 2017-07-04 09:04:34 -05:00			`\|`
Update tests 2019-03-09 06:03:44 -06:00			`LL \| $i as u32 < 0`
Use multispan suggestions more often * Use more accurate span for `async move` suggestion * Use more accurate span for deref suggestion * Use `multipart_suggestion` more often 2021-06-28 13:22:47 -05:00			`\| ^ - interpreted as generic arguments`
			`\| \|`
			`\| not interpreted as comparison`
syntax: Apply recovery for casts to type ascription Fix spans, add some comments 2017-07-03 18:17:01 -05:00			`...`
Update UI tests 2018-02-22 18:42:32 -06:00			`LL \| is_plainly_printable!(c);`
Bless tests 2021-10-14 13:28:28 -05:00			`\| ------------------------ in this macro invocation`
rustc_macros: don't limit the -Zmacro-backtrace suggestion to extern macros. 2019-12-16 07:56:47 -06:00			`\|`
Show macro name in 'this error originates in macro' message When there are multiple macros in use, it can be difficult to tell which one was responsible for producing an error. 2021-02-13 13:52:25 -06:00			= note: this error originates in the macro `is_plainly_printable` (in Nightly builds, run with -Z macro-backtrace for more info)
Use multispan suggestions more often * Use more accurate span for `async move` suggestion * Use more accurate span for deref suggestion * Use `multipart_suggestion` more often 2021-06-28 13:22:47 -05:00			`help: try comparing the cast value`
			`\|`
			`LL \| ($i as u32) < 0`
Modify structured suggestion output * On suggestions that include deletions, use a diff inspired output format * When suggesting addition, use `+` as underline * Color highlight modified span 2021-06-21 21:07:19 -05:00			`\| + +`
Fix spans for binary operator expression with interpolated identifiers 2017-07-04 09:04:34 -05:00
			`error: aborting due to previous error`