mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
10b08e3c9c
rust/tests/ui/async-await/issue-64130-non-send-future-diags.stderr

25 lines
897 B
Plaintext
Raw Normal View History

async/await: more improvements to non-send errors Signed-off-by: David Wood <david@davidtw.co>
2019-10-06 17:14:34 -05:00
error: future cannot be sent between threads safely
Feature gate and make must_not_suspend allow-by-default This lint is not yet ready for stable use, primarily due to false positives in edge cases; we want to test it out more before stabilizing.
2021-10-12 11:10:05 -05:00
--> $DIR/issue-64130-non-send-future-diags.rs:23:13
async/await: improve obligation errors This commit improves obligation errors for async/await: ``` note: future does not implement `std::marker::Send` because 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 `std::sync::MutexGuard<'_, u32>` LL | baz().await; | ^^^^^^^^^^^ await occurs here, with `g` maybe used later LL | } | - `g` is later dropped here ``` Signed-off-by: David Wood <david@davidtw.co>
2019-09-25 07:58:41 -05:00
|
LL | is_send(foo());
fix(rustc_typeck): report function argument errors on matching type Fixes #90101
2021-10-22 15:49:12 -05:00
| ^^^^^ future returned by `foo` is not `Send`
async/await: improve obligation errors This commit improves obligation errors for async/await: ``` note: future does not implement `std::marker::Send` because 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 `std::sync::MutexGuard<'_, u32>` LL | baz().await; | ^^^^^^^^^^^ await occurs here, with `g` maybe used later LL | } | - `g` is later dropped here ``` Signed-off-by: David Wood <david@davidtw.co>
2019-09-25 07:58:41 -05:00
|
Print output ty for opaque future ty
2021-11-16 18:16:23 -06:00
= help: within `impl Future<Output = ()>`, the trait `Send` is not implemented for `MutexGuard<'_, u32>`
async/await: more improvements to non-send errors Signed-off-by: David Wood <david@davidtw.co>
2019-10-06 17:14:34 -05:00
note: future is not `Send` as this value is used across an await
When `.await` is called on a non-`Future` expression, suggest removal Keep track of the origin of a `T: Future` obligation when caused by an `.await` expression. Address #66731.
2021-11-15 18:57:53 -06:00
--> $DIR/issue-64130-non-send-future-diags.rs:17:10
async/await: improve obligation errors This commit improves obligation errors for async/await: ``` note: future does not implement `std::marker::Send` because 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 `std::sync::MutexGuard<'_, u32>` LL | baz().await; | ^^^^^^^^^^^ await occurs here, with `g` maybe used later LL | } | - `g` is later dropped here ``` Signed-off-by: David Wood <david@davidtw.co>
2019-09-25 07:58:41 -05:00
|
LL | let g = x.lock().unwrap();
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
| - has type `MutexGuard<'_, u32>` which is not `Send`
async/await: improve obligation errors This commit improves obligation errors for async/await: ``` note: future does not implement `std::marker::Send` because 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 `std::sync::MutexGuard<'_, u32>` LL | baz().await; | ^^^^^^^^^^^ await occurs here, with `g` maybe used later LL | } | - `g` is later dropped here ``` Signed-off-by: David Wood <david@davidtw.co>
2019-09-25 07:58:41 -05:00
LL | baz().await;
When `.await` is called on a non-`Future` expression, suggest removal Keep track of the origin of a `T: Future` obligation when caused by an `.await` expression. Address #66731.
2021-11-15 18:57:53 -06:00
| ^^^^^^ await occurs here, with `g` maybe used later
async/await: improve obligation errors This commit improves obligation errors for async/await: ``` note: future does not implement `std::marker::Send` because 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 `std::sync::MutexGuard<'_, u32>` LL | baz().await; | ^^^^^^^^^^^ await occurs here, with `g` maybe used later LL | } | - `g` is later dropped here ``` Signed-off-by: David Wood <david@davidtw.co>
2019-09-25 07:58:41 -05:00
LL | }
| - `g` is later dropped here
Use note to point at bound introducing requirement
2021-07-31 11:26:55 -05:00
note: required by a bound in `is_send`
Feature gate and make must_not_suspend allow-by-default This lint is not yet ready for stable use, primarily due to false positives in edge cases; we want to test it out more before stabilizing.
2021-10-12 11:10:05 -05:00
--> $DIR/issue-64130-non-send-future-diags.rs:9:15
Use note to point at bound introducing requirement
2021-07-31 11:26:55 -05:00
|
LL | fn is_send<T: Send>(t: T) { }
| ^^^^ required by this bound in `is_send`
async/await: improve obligation errors This commit improves obligation errors for async/await: ``` note: future does not implement `std::marker::Send` because 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 `std::sync::MutexGuard<'_, u32>` LL | baz().await; | ^^^^^^^^^^^ await occurs here, with `g` maybe used later LL | } | - `g` is later dropped here ``` Signed-off-by: David Wood <david@davidtw.co>
2019-09-25 07:58:41 -05:00
error: aborting due to previous error
Reference in New Issue Copy Permalink