os-rust/tests/ui/borrowck/borrowck-use-in-index-lvalue.stderr

error[E0381]: used binding `w` isn't initialized
  --> $DIR/borrowck-use-in-index-lvalue.rs:3:5
   |
LL |     let w: &mut [isize];
   |         - binding declared here but left uninitialized
LL |     w[5] = 0;
   |     ^^^^ `*w` used here but it isn't initialized
   |
help: consider assigning a value
   |
LL |     let w: &mut [isize] = value;
   |                         +++++++

error[E0381]: used binding `w` isn't initialized
  --> $DIR/borrowck-use-in-index-lvalue.rs:6:5
   |
LL |     let mut w: &mut [isize];
   |         ----- binding declared here but left uninitialized
LL |     w[5] = 0;
   |     ^^^^ `*w` used here but it isn't initialized
   |
help: consider assigning a value
   |
LL |     let mut w: &mut [isize] = value;
   |                             +++++++

error: aborting due to 2 previous errors

For more information about this error, try `rustc --explain E0381`.
Wording tweak 2022-06-23 10:42:17 -07:00			error[E0381]: used binding `w` isn't initialized
update tests for migrate mode by default 2019-04-22 08:40:08 +01:00			`--> $DIR/borrowck-use-in-index-lvalue.rs:3:5`
Moved compile-fail tests to ui tests. 2018-08-08 14:28:26 +02: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 11:57:45 -07:00			`LL \| let w: &mut [isize];`
Tweak wording and spans 2022-06-21 15:54:17 -07:00			`\| - binding declared here but left uninitialized`
Updated UI test output to remove test annotations for revisions 2019-03-17 10:52:07 +01:00			`LL \| w[5] = 0;`
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 11:57:45 -07:00			\| ^^^^ `*w` used here but it isn't initialized
fix #102087, Suggest Default::default() when binding isn't initialized 2022-09-23 15:28:48 +08:00			`\|`
			`help: consider assigning a value`
			`\|`
Tweak value suggestions in `borrowck` and `hir_analysis` Unify the output of `suggest_assign_value` and `ty_kind_suggestion`. Ideally we'd make these a single function, but doing so would likely require modify the crate dependency tree. 2024-04-09 23:37:01 +00:00			`LL \| let w: &mut [isize] = value;`
			`\| +++++++`
Moved compile-fail tests to ui tests. 2018-08-08 14:28:26 +02:00
Wording tweak 2022-06-23 10:42:17 -07:00			error[E0381]: used binding `w` isn't initialized
update tests for migrate mode by default 2019-04-22 08:40:08 +01:00			`--> $DIR/borrowck-use-in-index-lvalue.rs:6:5`
Moved compile-fail tests to ui tests. 2018-08-08 14:28:26 +02: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 11:57:45 -07:00			`LL \| let mut w: &mut [isize];`
Tweak wording and spans 2022-06-21 15:54:17 -07:00			`\| ----- binding declared here but left uninitialized`
Updated UI test output to remove test annotations for revisions 2019-03-17 10:52:07 +01:00			`LL \| w[5] = 0;`
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 11:57:45 -07:00			\| ^^^^ `*w` used here but it isn't initialized
fix #102087, Suggest Default::default() when binding isn't initialized 2022-09-23 15:28:48 +08:00			`\|`
			`help: consider assigning a value`
			`\|`
Tweak value suggestions in `borrowck` and `hir_analysis` Unify the output of `suggest_assign_value` and `ty_kind_suggestion`. Ideally we'd make these a single function, but doing so would likely require modify the crate dependency tree. 2024-04-09 23:37:01 +00:00			`LL \| let mut w: &mut [isize] = value;`
			`\| +++++++`
Moved compile-fail tests to ui tests. 2018-08-08 14:28:26 +02:00
			`error: aborting due to 2 previous errors`

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