rust/tests/ui/loops/loop-proper-liveness.stderr

error[E0381]: used binding `x` isn't initialized
  --> $DIR/loop-proper-liveness.rs:9:22
   |
LL |     let x: i32;
   |         - binding declared here but left uninitialized
...
LL |     println!("{:?}", x);
   |                      ^ `x` used here but it isn't initialized
   |
   = note: this error originates in the macro `$crate::format_args_nl` which comes from the expansion of the macro `println` (in Nightly builds, run with -Z macro-backtrace for more info)
help: consider assigning a value
   |
LL |     let x: i32 = 42;
   |                ++++

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0381`.
Tweak wording and spans 2022-06-21 22:54:17 +00:00			error[E0381]: used binding `x` isn't initialized
Remove licenses 2018-12-25 15:56:47 +00:00			`--> $DIR/loop-proper-liveness.rs:9:22`
Moved compile-fail tests to ui tests. 2018-08-08 12:28:26 +00:00			`\|`
On partial uninit error point at where we need init When a binding is declared without a value, borrowck verifies that all codepaths have one assignment to them to initialize them fully. If there are any cases where a condition can be met that leaves the binding uninitialized or we attempt to initialize a field of an unitialized binding, we emit E0381. We now look at all the statements that initialize the binding, and use them to explore branching code paths that don't and point at them. If we find no potential places where an assignment to the binding might be missing, we display the spans of all the existing initializers to provide some context. 2022-06-21 18:57:45 +00:00			`LL \| let x: i32;`
Tweak wording and spans 2022-06-21 22:54:17 +00:00			`\| - binding declared here but left uninitialized`
On partial uninit error point at where we need init When a binding is declared without a value, borrowck verifies that all codepaths have one assignment to them to initialize them fully. If there are any cases where a condition can be met that leaves the binding uninitialized or we attempt to initialize a field of an unitialized binding, we emit E0381. We now look at all the statements that initialize the binding, and use them to explore branching code paths that don't and point at them. If we find no potential places where an assignment to the binding might be missing, we display the spans of all the existing initializers to provide some context. 2022-06-21 18:57:45 +00:00			`...`
Update tests 2019-03-09 12:03:44 +00:00			`LL \| println!("{:?}", x);`
Tweak wording and spans 2022-06-21 22:54:17 +00:00			\| ^ `x` used here but it isn't initialized
Fix a format_args span to be expansion 2021-10-21 14:01:16 +00:00			`\|`
Mention first and last macro in backtrace 2022-06-21 02:25:52 +00:00			= note: this error originates in the macro `$crate::format_args_nl` which comes from the expansion of the macro `println` (in Nightly builds, run with -Z macro-backtrace for more info)
fix #102087, Suggest Default::default() when binding isn't initialized 2022-09-23 07:28:48 +00:00			`help: consider assigning a value`
			`\|`
Handle more cases of value suggestions 2024-04-10 20:01:20 +00:00			`LL \| let x: i32 = 42;`
			`\| ++++`
Moved compile-fail tests to ui tests. 2018-08-08 12:28:26 +00: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`
Moved compile-fail tests to ui tests. 2018-08-08 12:28:26 +00:00
			For more information about this error, try `rustc --explain E0381`.