rust/tests/ui/closures/2229_closure_analysis/migrations/auto_traits.stderr

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

68 lines
3.1 KiB
Plaintext
Raw Normal View History

error: changes to closure capture in Rust 2021 will affect which traits the closure implements
2021-09-21 03:05:11 -05:00
--> $DIR/auto_traits.rs:22:19
|
2021-07-07 17:47:32 -05:00
LL | thread::spawn(move || unsafe {
2022-06-27 00:45:35 -05:00
| ^^^^^^^ in Rust 2018, this closure implements `Send` as `fptr` implements `Send`, but in Rust 2021, this closure will no longer implement `Send` because `fptr` is not fully captured and `fptr.0` does not implement `Send`
2021-07-07 17:47:32 -05:00
...
LL | *fptr.0 = 20;
| ------- in Rust 2018, this closure captures all of `fptr`, but in Rust 2021, it will only capture `fptr.0`
|
2022-09-18 10:55:36 -05:00
= note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/disjoint-capture-in-closures.html>
note: the lint level is defined here
--> $DIR/auto_traits.rs:2:9
|
LL | #![deny(rust_2021_incompatible_closure_captures)]
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
help: add a dummy let to cause `fptr` to be fully captured
|
LL ~ thread::spawn(move || { let _ = &fptr; unsafe {
2021-08-12 05:17:35 -05:00
LL |
...
2022-06-06 10:26:50 -05:00
LL |
2023-02-12 13:37:09 -06:00
LL ~ } }).join().unwrap();
2022-06-06 10:26:50 -05:00
|
error: changes to closure capture in Rust 2021 will affect which traits the closure implements
2021-09-21 03:05:11 -05:00
--> $DIR/auto_traits.rs:42:19
|
2021-07-07 17:47:32 -05:00
LL | thread::spawn(move || unsafe {
2022-06-27 00:45:35 -05:00
| ^^^^^^^
| |
2021-11-05 11:43:42 -05:00
| in Rust 2018, this closure implements `Send` as `fptr` implements `Send`, but in Rust 2021, this closure will no longer implement `Send` because `fptr` is not fully captured and `fptr.0.0` does not implement `Send`
| in Rust 2018, this closure implements `Sync` as `fptr` implements `Sync`, but in Rust 2021, this closure will no longer implement `Sync` because `fptr` is not fully captured and `fptr.0.0` does not implement `Sync`
2021-07-07 17:47:32 -05:00
...
LL | *fptr.0.0 = 20;
| --------- in Rust 2018, this closure captures all of `fptr`, but in Rust 2021, it will only capture `fptr.0.0`
|
= note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/disjoint-capture-in-closures.html>
help: add a dummy let to cause `fptr` to be fully captured
|
LL ~ thread::spawn(move || { let _ = &fptr; unsafe {
LL |
...
2022-06-06 10:26:50 -05:00
LL |
2023-02-12 13:37:09 -06:00
LL ~ } }).join().unwrap();
2022-06-06 10:26:50 -05:00
|
error: changes to closure capture in Rust 2021 will affect drop order and which traits the closure implements
--> $DIR/auto_traits.rs:67:13
|
2021-07-07 17:47:32 -05:00
LL | let c = || {
2021-11-05 11:43:42 -05:00
| ^^ in Rust 2018, this closure implements `Clone` as `f` implements `Clone`, but in Rust 2021, this closure will no longer implement `Clone` because `f` is not fully captured and `f.1` does not implement `Clone`
2021-07-07 17:47:32 -05:00
...
LL | let f_1 = f.1;
| --- in Rust 2018, this closure captures all of `f`, but in Rust 2021, it will only capture `f.1`
...
2021-07-07 17:47:32 -05:00
LL | }
| - in Rust 2018, `f` is dropped here, but in Rust 2021, only `f.1` will be dropped here as part of the closure
|
= note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/disjoint-capture-in-closures.html>
help: add a dummy let to cause `f` to be fully captured
|
2021-08-12 04:23:48 -05:00
LL ~ let c = || {
LL + let _ = &f;
2021-08-12 05:17:35 -05:00
|
error: aborting due to 3 previous errors