Description
I tried this code:
use std::sync::{Arc, Mutex};
use tokio::sync::Notify;
async fn good_fn() {
let m = Mutex::new(Arc::new(Notify::new()));
let v = m.lock().unwrap().clone();
v.notified().await;
}
async fn good_fn_2() {
let m = Mutex::new(Arc::new(Notify::new()));
let v = m.lock().unwrap();
let n = Arc::new(Notify::new());
drop(v);
n.notified().await;
}
async fn bad_fn() {
let m = Mutex::new(Arc::new(Notify::new()));
let inner = m.lock().unwrap();
let v = inner.clone();
drop(inner);
v.notified().await;
}
async fn bad_fn_2() {
let m = Mutex::new(true);
let inner = m.lock().unwrap();
let e = *inner == true;
let n = Arc::new(Notify::new());
drop(inner);
n.notified().await;
}
fn test_fn<F: Send + Sync>(f: F) {}
fn check() {
test_fn(good_fn());
test_fn(good_fn_2());
test_fn(bad_fn());
test_fn(bad_fn_2());
}I expected to see this happen: This should compile just fine
Instead, this happened: While the good_fn() and good_fn_2() compiles fine, the bad_fn() and bad_fn_2() reports that it's !Send, and thus can't be used.
The error is generally:
Note: future is not
Sendas this value is used across an await
Worth a note here: if I switch to tokio's mutex implementation, even when using blocking_lock(), this code compiles fine. Something about the rust standard MutexGuard seems to incorrectly be registered as being involved in the await.
It seems to be something about accessing any data on the mutex prior to the await point marks it as non-send, even when the data is explicitly dropped beforehand (and thus has no non-Send data surviving across any await point) so I think it's misreading this.
The Notify used in this example is from tokio with the sync feature enabled, but I'd imagine there are other simpler ways to trigger this too.
Meta
rustc --version --verbose:
rustc 1.86.0 (05f9846f8 2025-03-31)
binary: rustc
commit-hash: 05f9846f893b09a1be1fc8560e33fc3c815cfecb
commit-date: 2025-03-31
host: x86_64-unknown-linux-gnu
release: 1.86.0
LLVM version: 19.1.7
Backtrace
❯ RUST_BACKTRACE=1 cargo build
Compiling bug v0.1.0 (/bug)
warning: unused variable: `e`
--> src/lib.rs:29:9
|
29 | let e = *inner == true;
| ^ help: if this is intentional, prefix it with an underscore: `_e`
|
= note: `#[warn(unused_variables)]` on by default
error: future cannot be sent between threads safely
--> src/lib.rs:40:13
|
40 | test_fn(bad_fn());
| ^^^^^^^^ future returned by `bad_fn` is not `Send`
|
= help: within `impl Future<Output = ()>`, the trait `Send` is not implemented for `std::sync::MutexGuard<'_, Arc<Notify>>`
note: future is not `Send` as this value is used across an await
--> src/lib.rs:23:18
|
20 | let inner = m.lock().unwrap();
| ----- has type `std::sync::MutexGuard<'_, Arc<Notify>>` which is not `Send`
...
23 | v.notified().await;
| ^^^^^ await occurs here, with `inner` maybe used later
note: required by a bound in `test_fn`
--> src/lib.rs:35:15
|
35 | fn test_fn<F: Send + Sync>(f: F) {}
| ^^^^ required by this bound in `test_fn`
error: future cannot be sent between threads safely
--> src/lib.rs:41:13
|
41 | test_fn(bad_fn_2());
| ^^^^^^^^^^ future returned by `bad_fn_2` is not `Send`
|
= help: within `impl Future<Output = ()>`, the trait `Send` is not implemented for `std::sync::MutexGuard<'_, bool>`
note: future is not `Send` as this value is used across an await
--> src/lib.rs:32:18
|
28 | let inner = m.lock().unwrap();
| ----- has type `std::sync::MutexGuard<'_, bool>` which is not `Send`
...
32 | n.notified().await;
| ^^^^^ await occurs here, with `inner` maybe used later
note: required by a bound in `test_fn`
--> src/lib.rs:35:15
|
35 | fn test_fn<F: Send + Sync>(f: F) {}
| ^^^^ required by this bound in `test_fn`
warning: unused variable: `f`
--> src/lib.rs:35:28
|
35 | fn test_fn<F: Send + Sync>(f: F) {}
| ^ help: if this is intentional, prefix it with an underscore: `_f`
warning: `bug` (lib) generated 2 warnings
error: could not compile `bug` (lib) due to 2 previous errors; 2 warnings emitted