07e7823c01
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.
23 lines
783 B
Plaintext
23 lines
783 B
Plaintext
error: future cannot be sent between threads safely
|
|
--> $DIR/issue-64130-non-send-future-diags.rs:21:5
|
|
|
|
|
LL | fn is_send<T: Send>(t: T) { }
|
|
| ---- required by this bound in `is_send`
|
|
...
|
|
LL | is_send(foo());
|
|
| ^^^^^^^ future returned by `foo` is not `Send`
|
|
|
|
|
= help: within `impl Future`, the trait `Send` is not implemented for `MutexGuard<'_, u32>`
|
|
note: future is not `Send` as this value is used across an await
|
|
--> $DIR/issue-64130-non-send-future-diags.rs:15:5
|
|
|
|
|
LL | let g = x.lock().unwrap();
|
|
| - has type `MutexGuard<'_, u32>` which is not `Send`
|
|
LL | baz().await;
|
|
| ^^^^^^^^^^^ await occurs here, with `g` maybe used later
|
|
LL | }
|
|
| - `g` is later dropped here
|
|
|
|
error: aborting due to previous error
|
|
|