rust/tests/ui/try-block/try-block-opt-init.stderr

error[E0381]: used binding `cfg_res` is possibly-uninitialized
  --> $DIR/try-block-opt-init.rs:15:5
   |
LL |     let cfg_res;
   |         ------- binding declared here but left uninitialized
...
LL |         cfg_res = 5;
   |         ----------- binding initialized here in some conditions
...
LL |     assert_eq!(cfg_res, 5);
   |     ^^^^^^^^^^^^^^^^^^^^^^ `cfg_res` used here but it is possibly-uninitialized
   |
   = note: this error originates in the macro `assert_eq` (in Nightly builds, run with -Z macro-backtrace for more info)

error: aborting due to previous error

For more information about this error, try `rustc --explain E0381`.
Review comments: wording 2022-06-22 11:04:36 -07:00			error[E0381]: used binding `cfg_res` is possibly-uninitialized
Remove licenses 2018-12-25 08:56:47 -07:00			`--> $DIR/try-block-opt-init.rs:15:5`
Make a try-blocks folder for all the try{} UI tests 2018-08-12 20:05:29 -07: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 cfg_res;`
Tweak wording and spans 2022-06-21 15:54:17 -07: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 11:57:45 -07:00			`...`
			`LL \| cfg_res = 5;`
			`\| ----------- binding initialized here in some conditions`
			`...`
Update tests 2019-03-09 15:03:44 +03:00			`LL \| assert_eq!(cfg_res, 5);`
Review comments: wording 2022-06-22 11:04:36 -07:00			\| ^^^^^^^^^^^^^^^^^^^^^^ `cfg_res` used here but it is possibly-uninitialized
Make a try-blocks folder for all the try{} UI tests 2018-08-12 20:05:29 -07:00			`\|`
Show macro name in 'this error originates in macro' message When there are multiple macros in use, it can be difficult to tell which one was responsible for producing an error. 2021-02-13 14:52:25 -05:00			= note: this error originates in the macro `assert_eq` (in Nightly builds, run with -Z macro-backtrace for more info)
Make a try-blocks folder for all the try{} UI tests 2018-08-12 20:05:29 -07:00
			`error: aborting due to previous error`

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