rust/tests/ui/consts/non-const-value-in-const.stderr

error[E0435]: attempt to use a non-constant value in a constant
  --> $DIR/non-const-value-in-const.rs:3:20
   |
LL |     const Y: i32 = x;
   |                    ^ non-constant value
   |
help: consider using `let` instead of `const`
   |
LL |     let Y: i32 = x;
   |     ~~~

error[E0435]: attempt to use a non-constant value in a constant
  --> $DIR/non-const-value-in-const.rs:6:17
   |
LL |     let _ = [0; x];
   |                 ^ non-constant value
   |
help: consider using `const` instead of `let`
   |
LL |     const x: /* Type */ = 5;
   |     ~~~~~  ++++++++++++

error: aborting due to 2 previous errors

For more information about this error, try `rustc --explain E0435`.
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 13:40:29 -06:00			`error[E0435]: attempt to use a non-constant value in a constant`
			`--> $DIR/non-const-value-in-const.rs:3:20`
			`\|`
			`LL \| const Y: i32 = x;`
Use verbose style when suggesting changing `const` with `let` 2024-07-05 14:32:17 -05:00			`\| ^ non-constant value`
			`\|`
			help: consider using `let` instead of `const`
			`\|`
			`LL \| let Y: i32 = 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 13:40:29 -06:00
			`error[E0435]: attempt to use a non-constant value in a constant`
			`--> $DIR/non-const-value-in-const.rs:6:17`
			`\|`
			`LL \| let _ = [0; x];`
			`\| ^ non-constant value`
Use verbose style when suggesting changing `const` with `let` 2024-07-05 14:32:17 -05:00			`\|`
			help: consider using `const` instead of `let`
			`\|`
Account for `let foo = expr`; to suggest `const foo: Ty = expr;` 2024-07-08 14:43:20 -05:00			`LL \| const x: /* Type */ = 5;`
			`\| ~~~~~ ++++++++++++`
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 13:40:29 -06:00
			`error: aborting due to 2 previous errors`

			For more information about this error, try `rustc --explain E0435`.