add test for correct await span

This commit is contained in:
csmoe 2020-04-16 23:14:11 +08:00
parent bc1595473b
commit 00d12ef901
5 changed files with 62 additions and 12 deletions

View file

@ -0,0 +1,21 @@
// edition:2018
use std::future::Future;
use std::sync::Mutex;
fn fake_spawn<F: Future + Send + 'static>(f: F) { }
async fn wrong_mutex() {
let m = Mutex::new(1);
{
let mut guard = m.lock().unwrap();
(async { "right"; }).await;
*guard += 1;
}
(async { "wrong"; }).await;
}
fn main() {
fake_spawn(wrong_mutex()); //~ Error future cannot be sent between threads safely
}

View file

@ -0,0 +1,23 @@
error: future cannot be sent between threads safely
--> $DIR/issue-71137.rs:20:3
|
LL | fn fake_spawn<F: Future + Send + 'static>(f: F) { }
| ---- required by this bound in `fake_spawn`
...
LL | fake_spawn(wrong_mutex());
| ^^^^^^^^^^ future returned by `wrong_mutex` is not `Send`
|
= help: within `impl std::future::Future`, the trait `std::marker::Send` is not implemented for `std::sync::MutexGuard<'_, i32>`
note: future is not `Send` as this value is used across an await
--> $DIR/issue-71137.rs:12:5
|
LL | let mut guard = m.lock().unwrap();
| --------- has type `std::sync::MutexGuard<'_, i32>` which is not `Send`
LL | (async { "right"; }).await;
| ^^^^^^^^^^^^^^^^^^^^^^^^^^ await occurs here, with `mut guard` maybe used later
LL | *guard += 1;
LL | }
| - `mut guard` is later dropped here
error: aborting due to previous error