rust/src/test/ui/async-await/partial-initialization-across-await.stderr

error[E0381]: assign to part of possibly uninitialized variable: `t`
  --> $DIR/partial-initialization-across-await.rs:15:5
   |
LL |     t.0 = 42;
   |     ^^^^^^^^ use of possibly uninitialized `t`

error[E0381]: assign to part of possibly uninitialized variable: `t`
  --> $DIR/partial-initialization-across-await.rs:24:5
   |
LL |     t.0 = 42;
   |     ^^^^^^^^ use of possibly uninitialized `t`

error[E0381]: assign to part of possibly uninitialized variable: `t`
  --> $DIR/partial-initialization-across-await.rs:33:5
   |
LL |     t.x = 42;
   |     ^^^^^^^^ use of possibly uninitialized `t`

error: aborting due to 3 previous errors

For more information about this error, try `rustc --explain E0381`.
Make use of possibly uninitialized data a hard error This is one of the behaviors we no longer allow in NLL. Since it can lead to undefined behavior, I think it's definitely worth making it a hard error without waiting to turn off migration mode (#58781). Closes #60450. My ulterior motive here is making it impossible to leave variables partially initialized across a yield (see discussion at #63035), so tests are included for that. 2019-08-03 00:08:16 +00:00			error[E0381]: assign to part of possibly uninitialized variable: `t`
			`--> $DIR/partial-initialization-across-await.rs:15:5`
			`\|`
			`LL \| t.0 = 42;`
			\| ^^^^^^^^ use of possibly uninitialized `t`

			error[E0381]: assign to part of possibly uninitialized variable: `t`
			`--> $DIR/partial-initialization-across-await.rs:24:5`
			`\|`
			`LL \| t.0 = 42;`
			\| ^^^^^^^^ use of possibly uninitialized `t`

			error[E0381]: assign to part of possibly uninitialized variable: `t`
			`--> $DIR/partial-initialization-across-await.rs:33:5`
			`\|`
			`LL \| t.x = 42;`
			\| ^^^^^^^^ use of possibly uninitialized `t`

			`error: aborting due to 3 previous errors`

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