mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
12ddf77811
rust/tests/ui/closures/closure-move-sync.stderr

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

44 lines
1.6 KiB
Plaintext
Raw Normal View History

Suggest using `move` when trying to share `...::channel::{Receiver, Sender}` Extend `rustc_on_unimplemented` to match on ADT without evaluating type arguments.
2018-02-11 15:39:32 -06:00
error[E0277]: `std::sync::mpsc::Receiver<()>` cannot be shared between threads safely
Rework point-at-arg
2022-08-16 01:27:22 -05:00
--> $DIR/closure-move-sync.rs:6:27
Suggest using `move` when trying to share `...::channel::{Receiver, Sender}` Extend `rustc_on_unimplemented` to match on ADT without evaluating type arguments.
2018-02-11 15:39:32 -06:00
|
Rework point-at-arg
2022-08-16 01:27:22 -05:00
LL | let t = thread::spawn(|| {
| _____________-------------_^
| | |
| | required by a bound introduced by this call
LL | | recv.recv().unwrap();
LL | |
LL | | });
| |_____^ `std::sync::mpsc::Receiver<()>` cannot be shared between threads safely
Remove trailing whitespace from error messages
2021-06-10 06:52:00 -05:00
|
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 02:40:56 -05:00
= help: the trait `Sync` is not implemented for `std::sync::mpsc::Receiver<()>`
Reword "Required because of the requirements on the impl of ..."
2022-08-15 15:31:37 -05:00
= note: required for `&std::sync::mpsc::Receiver<()>` to implement `Send`
Greatly improve error reporting for futures and generators in `note_obligation_cause_code` Most futures don't go through this code path, because they're caught by `maybe_note_obligation_cause_for_async_await`. But all generators do, and `maybe_note` is imperfect and doesn't catch all futures. Improve the error message for those it misses. At some point, we may want to consider unifying this with the code for `maybe_note_async_await`, so that `async_await` notes all parent constraints, and `note_obligation` can point to yield points. But both functions are quite complicated, and it's not clear to me how to combine them; this seems like a good incremental improvement.
2022-06-19 13:59:36 -05:00
note: required because it's used within this closure
--> $DIR/closure-move-sync.rs:6:27
|
Shorten span for closures.
2022-06-27 00:45:35 -05:00
LL | let t = thread::spawn(|| {
| ^^
Use note to point at bound introducing requirement
2021-07-31 11:26:55 -05:00
note: required by a bound in `spawn`
--> $SRC_DIR/std/src/thread/mod.rs:LL:COL
Suggest using `move` when trying to share `...::channel::{Receiver, Sender}` Extend `rustc_on_unimplemented` to match on ADT without evaluating type arguments.
2018-02-11 15:39:32 -06:00
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 02:40:56 -05:00
error[E0277]: `Sender<()>` cannot be shared between threads safely
Rework point-at-arg
2022-08-16 01:27:22 -05:00
--> $DIR/closure-move-sync.rs:18:19
Suggest using `move` when trying to share `...::channel::{Receiver, Sender}` Extend `rustc_on_unimplemented` to match on ADT without evaluating type arguments.
2018-02-11 15:39:32 -06:00
|
Review comment: remove mention of `move` closure
2018-02-25 15:18:29 -06:00
LL | thread::spawn(|| tx.send(()).unwrap());
Rework point-at-arg
2022-08-16 01:27:22 -05:00
| ------------- ^^^^^^^^^^^^^^^^^^^^^^^ `Sender<()>` cannot be shared between threads safely
| |
| required by a bound introduced by this call
Remove trailing whitespace from error messages
2021-06-10 06:52:00 -05:00
|
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 02:40:56 -05:00
= help: the trait `Sync` is not implemented for `Sender<()>`
Reword "Required because of the requirements on the impl of ..."
2022-08-15 15:31:37 -05:00
= note: required for `&Sender<()>` to implement `Send`
Greatly improve error reporting for futures and generators in `note_obligation_cause_code` Most futures don't go through this code path, because they're caught by `maybe_note_obligation_cause_for_async_await`. But all generators do, and `maybe_note` is imperfect and doesn't catch all futures. Improve the error message for those it misses. At some point, we may want to consider unifying this with the code for `maybe_note_async_await`, so that `async_await` notes all parent constraints, and `note_obligation` can point to yield points. But both functions are quite complicated, and it's not clear to me how to combine them; this seems like a good incremental improvement.
2022-06-19 13:59:36 -05:00
note: required because it's used within this closure
--> $DIR/closure-move-sync.rs:18:19
|
LL | thread::spawn(|| tx.send(()).unwrap());
Shorten span for closures.
2022-06-27 00:45:35 -05:00
| ^^
Use note to point at bound introducing requirement
2021-07-31 11:26:55 -05:00
note: required by a bound in `spawn`
--> $SRC_DIR/std/src/thread/mod.rs:LL:COL
Suggest using `move` when trying to share `...::channel::{Receiver, Sender}` Extend `rustc_on_unimplemented` to match on ADT without evaluating type arguments.
2018-02-11 15:39:32 -06:00
error: aborting due to 2 previous errors
Add span label to E0044
2018-03-14 20:10:25 -05:00
For more information about this error, try `rustc --explain E0277`.
Reference in New Issue Copy Permalink