dnrops
/
rust
mirror of https://github.com/rust-lang/rust.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
rust/tests/ui/no-send-res-ports.stderr

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

38 lines
1.2 KiB
Plaintext
Raw Normal View History

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 15:40:56 +08:00
error[E0277]: `Rc<()>` cannot be sent between threads safely
Rework point-at-arg
2022-08-16 14:27:22 +08:00
--> $DIR/no-send-res-ports.rs:25:19
Moved compile-fail tests to ui tests.
2018-08-08 20:28:26 +08:00
|
Rework point-at-arg
2022-08-16 14:27:22 +08:00
LL | thread::spawn(move|| {
| ------------- ^-----
| | |
adjust how closure/generator types and rvalues are printed
2023-09-09 14:36:50 +08:00
| _____|_____________within this `{closure@$DIR/no-send-res-ports.rs:25:19: 25:25}`
Rework point-at-arg
2022-08-16 14:27:22 +08:00
| | |
| | required by a bound introduced by this call
LL | |
LL | | let y = x;
LL | | println!("{:?}", y);
LL | | });
| |_____^ `Rc<()>` cannot be sent between threads safely
Remove trailing whitespace from error messages
2021-06-10 19:52:00 +08:00
|
adjust how closure/generator types and rvalues are printed
2023-09-09 14:36:50 +08:00
= help: within `{closure@$DIR/no-send-res-ports.rs:25:19: 25:25}`, the trait `Send` is not implemented for `Rc<()>`
Point at `impl` and type defs introducing requirements on E0277
2021-03-31 04:37:30 +08:00
note: required because it appears within the type `Port<()>`
--> $DIR/no-send-res-ports.rs:5:8
|
LL | struct Port<T>(Rc<T>);
| ^^^^
note: required because it appears within the type `Foo`
--> $DIR/no-send-res-ports.rs:9:12
|
LL | struct Foo {
| ^^^
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-20 02:59:36 +08:00
note: required because it's used within this closure
--> $DIR/no-send-res-ports.rs:25:19
|
Shorten span for closures.
2022-06-27 13:45:35 +08:00
LL | thread::spawn(move|| {
| ^^^^^^
Use note to point at bound introducing requirement
2021-08-01 00:26:55 +08:00
note: required by a bound in `spawn`
--> $SRC_DIR/std/src/thread/mod.rs:LL:COL
Moved compile-fail tests to ui tests.
2018-08-08 20:28:26 +08:00
error: aborting due to previous error
For more information about this error, try `rustc --explain E0277`.