os-rust/tests/ui/consts/issue-3521.stderr

error[E0435]: attempt to use a non-constant value in a constant
  --> $DIR/issue-3521.rs:8:15
   |
LL |         Bar = foo
   |               ^^^ non-constant value
   |
help: consider using `const` instead of `let`
   |
LL |     const foo: isize = 100;
   |     ~~~~~

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0435`.
Move some `compile-fail` tests to `ui` 2018-07-15 14:11:54 -07:00			`error[E0435]: attempt to use a non-constant value in a constant`
Use correct span for structured suggestion On structured suggestion for `let` -> `const` and `const` -> `let`, use a proper `Span` and update tests to check the correct application. Follow up to #80012. 2021-01-07 16:44:08 -08:00			`--> $DIR/issue-3521.rs:8:15`
Move some `compile-fail` tests to `ui` 2018-07-15 14:11:54 -07:00			`\|`
			`LL \| Bar = foo`
			`\| ^^^ non-constant value`
Use verbose style when suggesting changing `const` with `let` 2024-07-05 19:32:17 +00:00			`\|`
			help: consider using `const` instead of `let`
			`\|`
			`LL \| const foo: isize = 100;`
			`\| ~~~~~`
Move some `compile-fail` tests to `ui` 2018-07-15 14:11:54 -07:00
Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 15:44:16 +00:00			`error: aborting due to 1 previous error`
Move some `compile-fail` tests to `ui` 2018-07-15 14:11:54 -07:00
			For more information about this error, try `rustc --explain E0435`.