rust/tests/ui/borrowck/assign_mutable_fields.stderr

error[E0381]: partially assigned binding `x` isn't fully initialized
  --> $DIR/assign_mutable_fields.rs:9:5
   |
LL |     let mut x: (u32, u32);
   |         ----- binding declared here but left uninitialized
LL |     x.0 = 1;
   |     ^^^^^^^ `x` partially assigned here but it isn't fully initialized
   |
   = help: partial initialization isn't supported, fully initialize the binding with a default value and mutate it, or use `std::mem::MaybeUninit`

error[E0381]: partially assigned binding `x` isn't fully initialized
  --> $DIR/assign_mutable_fields.rs:17:5
   |
LL |     let mut x: (u32, u32);
   |         ----- binding declared here but left uninitialized
LL |     x.0 = 1;
   |     ^^^^^^^ `x` partially assigned here but it isn't fully initialized
   |
   = help: partial initialization isn't supported, fully initialize the binding with a default value and mutate it, or use `std::mem::MaybeUninit`

error: aborting due to 2 previous errors

For more information about this error, try `rustc --explain E0381`.
Tweak wording and spans 2022-06-21 17:54:17 -05:00			error[E0381]: partially assigned binding `x` isn't fully initialized
update tests for migrate mode by default 2019-04-22 02:40:08 -05:00			`--> $DIR/assign_mutable_fields.rs:9:5`
move tests to borrowck directory, remove feature(nll) now compare-mode can show us the differences 2018-08-14 07:24:44 -05: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 13:57:45 -05:00			`LL \| let mut x: (u32, u32);`
Tweak wording and spans 2022-06-21 17:54:17 -05:00			`\| ----- binding declared here but left uninitialized`
update tests for migrate mode by default 2019-04-22 02:40:08 -05:00			`LL \| x.0 = 1;`
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 13:57:45 -05:00			\| ^^^^^^^ `x` partially assigned here but it isn't fully initialized
			`\|`
Tweak wording and spans 2022-06-21 17:54:17 -05:00			= help: partial initialization isn't supported, fully initialize the binding with a default value and mutate it, or use `std::mem::MaybeUninit`
move tests to borrowck directory, remove feature(nll) now compare-mode can show us the differences 2018-08-14 07:24:44 -05:00
Tweak wording and spans 2022-06-21 17:54:17 -05:00			error[E0381]: partially assigned binding `x` isn't fully initialized
update tests for migrate mode by default 2019-04-22 02:40:08 -05:00			`--> $DIR/assign_mutable_fields.rs:17:5`
move tests to borrowck directory, remove feature(nll) now compare-mode can show us the differences 2018-08-14 07:24:44 -05: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 13:57:45 -05:00			`LL \| let mut x: (u32, u32);`
Tweak wording and spans 2022-06-21 17:54:17 -05:00			`\| ----- binding declared here but left uninitialized`
update tests for migrate mode by default 2019-04-22 02:40:08 -05:00			`LL \| x.0 = 1;`
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 13:57:45 -05:00			\| ^^^^^^^ `x` partially assigned here but it isn't fully initialized
			`\|`
Tweak wording and spans 2022-06-21 17:54:17 -05:00			= help: partial initialization isn't supported, fully initialize the binding with a default value and mutate it, or use `std::mem::MaybeUninit`
move tests to borrowck directory, remove feature(nll) now compare-mode can show us the differences 2018-08-14 07:24:44 -05:00
update tests for migrate mode by default 2019-04-22 02:40:08 -05:00			`error: aborting due to 2 previous errors`
move tests to borrowck directory, remove feature(nll) now compare-mode can show us the differences 2018-08-14 07:24:44 -05:00
			For more information about this error, try `rustc --explain E0381`.