rust/src/test/ui/nll/match-cfg-fake-edges.stderr

error[E0381]: used binding `x` isn't initialized
  --> $DIR/match-cfg-fake-edges.rs:21:13
   |
LL |     let x;
   |         - binding declared here but left uninitialized
...
LL |         _ if { x = 2; true } => 1,
   |                ----- binding initialized here in some conditions
LL |         _ if {
LL |             x;
   |             ^ `x` used here but it isn't initialized

error[E0382]: use of moved value: `x`
  --> $DIR/match-cfg-fake-edges.rs:35:13
   |
LL |     let x = String::new();
   |         - move occurs because `x` has type `String`, which does not implement the `Copy` trait
...
LL |         false if { drop(x); true } => 1,
   |                         - value moved here
LL |         true => {
LL |             x;
   |             ^ value used here after move

error: aborting due to 2 previous errors

Some errors have detailed explanations: E0381, E0382.
For more information about an error, try `rustc --explain E0381`.
Avoid misleading message/label in `match-cfg-fake-edges.rs` test 2022-06-22 19:59:48 +00:00			error[E0381]: used binding `x` isn't initialized
Update tests wrt. bind_by_by_move_pattern_guards stabilization. 2019-07-29 23:25:30 +00:00			`--> $DIR/match-cfg-fake-edges.rs:21:13`
Improve error message and add tests for borrowck match handling 2019-02-02 10:45:20 +00: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 18:57:45 +00:00			`LL \| let x;`
Tweak wording and spans 2022-06-21 22:54:17 +00: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 18:57:45 +00:00			`...`
Avoid misleading message/label in `match-cfg-fake-edges.rs` test 2022-06-22 19:59:48 +00:00			`LL \| _ if { x = 2; true } => 1,`
			`\| ----- binding initialized here in some conditions`
			`LL \| _ if {`
Update tests 2019-03-09 12:03:44 +00:00			`LL \| x;`
Avoid misleading message/label in `match-cfg-fake-edges.rs` test 2022-06-22 19:59:48 +00:00			\| ^ `x` used here but it isn't initialized
Improve error message and add tests for borrowck match handling 2019-02-02 10:45:20 +00:00
			error[E0382]: use of moved value: `x`
Update tests wrt. bind_by_by_move_pattern_guards stabilization. 2019-07-29 23:25:30 +00:00			`--> $DIR/match-cfg-fake-edges.rs:35:13`
Improve error message and add tests for borrowck match handling 2019-02-02 10:45:20 +00:00			`\|`
			`LL \| let x = String::new();`
pretty: trim paths of unique symbols If a symbol name can only be imported from one place for a type, and as long as it was not glob-imported anywhere in the current crate, we can trim its printed path and print only the name. This has wide implications on error messages with types, for example, shortening `std::vec::Vec` to just `Vec`, as long as there is no other `Vec` importable anywhere. This adds a new '-Z trim-diagnostic-paths=false' option to control this feature. On the good path, with no diagnosis printed, we should try to avoid issuing this query, so we need to prevent trimmed_def_paths query on several cases. This change also relies on a previous commit that differentiates between `Debug` and `Display` on various rustc types, where the latter is trimmed and presented to the user and the former is not. 2020-09-02 07:40:56 +00:00			\| - move occurs because `x` has type `String`, which does not implement the `Copy` trait
Improve error message and add tests for borrowck match handling 2019-02-02 10:45:20 +00:00			`...`
			`LL \| false if { drop(x); true } => 1,`
			`\| - value moved here`
			`LL \| true => {`
Update tests 2019-03-09 12:03:44 +00:00			`LL \| x;`
Improve error message and add tests for borrowck match handling 2019-02-02 10:45:20 +00:00			`\| ^ value used here after move`

Remove 'feature(nll)' from bind_by_move_pattern_guards tests. 2019-07-27 22:56:36 +00:00			`error: aborting due to 2 previous errors`
Improve error message and add tests for borrowck match handling 2019-02-02 10:45:20 +00:00
Remove 'feature(nll)' from bind_by_move_pattern_guards tests. 2019-07-27 22:56:36 +00:00			`Some errors have detailed explanations: E0381, E0382.`
Improve error message and add tests for borrowck match handling 2019-02-02 10:45:20 +00:00			For more information about an error, try `rustc --explain E0381`.