mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
374024336a
rust/tests/ui/nll/issue-21232-partial-init-and-erroneous-use.stderr

65 lines
2.7 KiB
Plaintext
Raw Normal View History

Fix label on uninit binding field assignment
2022-06-22 17:36:26 -05:00
error[E0381]: assigned binding `d` isn't fully initialized
Remove feature(nll) when compare mode is sufficient
2019-04-07 10:07:36 -05:00
--> $DIR/issue-21232-partial-init-and-erroneous-use.rs:28:5
Some new tests I added.
2018-10-11 18:33:08 -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 d: D;
Tweak wording and spans
2022-06-21 17:54:17 -05:00
| - binding declared here but left uninitialized
Some new tests I added.
2018-10-11 18:33:08 -05:00
LL | d.x = 10;
Fix label on uninit binding field assignment
2022-06-22 17:36:26 -05:00
| ^^^^^^^^ `d` assigned here but it isn't fully initialized
Wording tweak
2022-06-23 12:42: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`
Some new tests I added.
2018-10-11 18:33:08 -05:00
Fix label on uninit binding field assignment
2022-06-22 17:36:26 -05:00
error[E0381]: assigned binding `d` isn't fully initialized
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
--> $DIR/issue-21232-partial-init-and-erroneous-use.rs:33:5
Some new tests I added.
2018-10-11 18:33:08 -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 d: D;
Tweak wording and spans
2022-06-21 17:54:17 -05:00
| ----- binding declared here but left uninitialized
Some new tests I added.
2018-10-11 18:33:08 -05:00
LL | d.x = 10;
Fix label on uninit binding field assignment
2022-06-22 17:36:26 -05:00
| ^^^^^^^^ `d` assigned here but it isn't fully initialized
Wording tweak
2022-06-23 12:42: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`
Some new tests I added.
2018-10-11 18:33:08 -05:00
error[E0382]: assign of moved value: `d`
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
--> $DIR/issue-21232-partial-init-and-erroneous-use.rs:39:5
Some new tests I added.
2018-10-11 18:33:08 -05:00
|
When using value after move, point at span of local When trying to use a value after move, instead of using a note, point at the local declaration that has a type that doesn't implement `Copy` trait.
2019-01-02 18:43:08 -06:00
LL | let mut d = D { x: 0, s: S{ y: 0, z: 0 } };
| ----- move occurs because `d` has type `D`, which does not implement the `Copy` trait
Some new tests I added.
2018-10-11 18:33:08 -05:00
LL | drop(d);
| - value moved here
LL | d.x = 10;
| ^^^^^^^^ value assigned here after move
Wording tweak
2022-06-23 12:42:17 -05:00
error[E0381]: partially assigned binding `d` isn't fully initialized
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
--> $DIR/issue-21232-partial-init-and-erroneous-use.rs:45:5
Some new tests I added.
2018-10-11 18:33:08 -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 d: D;
Tweak wording and spans
2022-06-21 17:54:17 -05:00
| - binding declared here but left uninitialized
Some new tests I added.
2018-10-11 18:33:08 -05:00
LL | d.s.y = 20;
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
| ^^^^^^^^^^ `d.s` 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`
Some new tests I added.
2018-10-11 18:33:08 -05:00
Wording tweak
2022-06-23 12:42:17 -05:00
error[E0381]: partially assigned binding `d` isn't fully initialized
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
--> $DIR/issue-21232-partial-init-and-erroneous-use.rs:50:5
Some new tests I added.
2018-10-11 18:33:08 -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 d: D;
Tweak wording and spans
2022-06-21 17:54:17 -05:00
| ----- binding declared here but left uninitialized
Some new tests I added.
2018-10-11 18:33:08 -05:00
LL | d.s.y = 20;
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
| ^^^^^^^^^^ `d.s` 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`
Some new tests I added.
2018-10-11 18:33:08 -05:00
error[E0382]: assign to part of moved value: `d`
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
--> $DIR/issue-21232-partial-init-and-erroneous-use.rs:56:5
Some new tests I added.
2018-10-11 18:33:08 -05:00
|
When using value after move, point at span of local When trying to use a value after move, instead of using a note, point at the local declaration that has a type that doesn't implement `Copy` trait.
2019-01-02 18:43:08 -06:00
LL | let mut d = D { x: 0, s: S{ y: 0, z: 0} };
| ----- move occurs because `d` has type `D`, which does not implement the `Copy` trait
Some new tests I added.
2018-10-11 18:33:08 -05:00
LL | drop(d);
| - value moved here
LL | d.s.y = 20;
| ^^^^^^^^^^ value partially assigned here after move
error: aborting due to 6 previous errors
hide `--explain` hint if error has no extended info
2019-04-17 12:26:38 -05:00
Some errors have detailed explanations: E0381, E0382.
Some new tests I added.
2018-10-11 18:33:08 -05:00
For more information about an error, try `rustc --explain E0381`.
Reference in New Issue Copy Permalink