rust/tests/ui/rfc-2497-if-let-chains/chains-without-let.stderr

error[E0381]: used binding `z` is possibly-uninitialized
  --> $DIR/chains-without-let.rs:3:34
   |
LL |     let z;
   |         - binding declared here but left uninitialized
LL |     if true && { z = 3; true} && z == 3 {}
   |                  -----           ^ `z` used here but it is possibly-uninitialized
   |                  |
   |                  binding initialized here in some conditions

error[E0381]: used binding `z` is possibly-uninitialized
  --> $DIR/chains-without-let.rs:9:31
   |
LL |     let z;
   |         - binding declared here but left uninitialized
LL |     true && { z = 3; true} && z == 3;
   |               -----           ^ `z` used here but it is possibly-uninitialized
   |               |
   |               binding initialized here in some conditions

error[E0381]: used binding `z` is possibly-uninitialized
  --> $DIR/chains-without-let.rs:15:36
   |
LL |     let z;
   |         - binding declared here but left uninitialized
LL |     if false || { z = 3; false} || z == 3 {}
   |                   -----            ^ `z` used here but it is possibly-uninitialized
   |                   |
   |                   binding initialized here in some conditions

error: aborting due to 3 previous errors

For more information about this error, try `rustc --explain E0381`.
Review comments: wording 2022-06-22 13:04:36 -05:00			error[E0381]: used binding `z` is possibly-uninitialized
Formally implement let chains 2022-01-18 16:38:17 -06:00			`--> $DIR/chains-without-let.rs:3:34`
			`\|`
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 z;`
Tweak wording and spans 2022-06-21 17:54:17 -05:00			`\| - binding declared here but left uninitialized`
Formally implement let chains 2022-01-18 16:38:17 -06:00			`LL \| if true && { z = 3; true} && z == 3 {}`
Review comments: wording 2022-06-22 13:04:36 -05:00			\| ----- ^ `z` used here but it is possibly-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 13:57:45 -05:00			`\| \|`
			`\| binding initialized here in some conditions`
Formally implement let chains 2022-01-18 16:38:17 -06:00
Review comments: wording 2022-06-22 13:04:36 -05:00			error[E0381]: used binding `z` is possibly-uninitialized
Formally implement let chains 2022-01-18 16:38:17 -06:00			`--> $DIR/chains-without-let.rs:9:31`
			`\|`
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 z;`
Tweak wording and spans 2022-06-21 17:54:17 -05:00			`\| - binding declared here but left uninitialized`
Formally implement let chains 2022-01-18 16:38:17 -06:00			`LL \| true && { z = 3; true} && z == 3;`
Review comments: wording 2022-06-22 13:04:36 -05:00			\| ----- ^ `z` used here but it is possibly-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 13:57:45 -05:00			`\| \|`
			`\| binding initialized here in some conditions`
Formally implement let chains 2022-01-18 16:38:17 -06:00
Review comments: wording 2022-06-22 13:04:36 -05:00			error[E0381]: used binding `z` is possibly-uninitialized
Formally implement let chains 2022-01-18 16:38:17 -06:00			`--> $DIR/chains-without-let.rs:15:36`
			`\|`
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 z;`
Tweak wording and spans 2022-06-21 17:54:17 -05:00			`\| - binding declared here but left uninitialized`
Formally implement let chains 2022-01-18 16:38:17 -06:00			`LL \| if false \|\| { z = 3; false} \|\| z == 3 {}`
Review comments: wording 2022-06-22 13:04:36 -05:00			\| ----- ^ `z` used here but it is possibly-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 13:57:45 -05:00			`\| \|`
			`\| binding initialized here in some conditions`
Formally implement let chains 2022-01-18 16:38:17 -06:00
			`error: aborting due to 3 previous errors`

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