diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2024-12-03 17:27:05 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-12-03 17:27:05 +0100 |
| commit | c179a15f7a0a459521022f5aadc10125a33c6efb (patch) | |
| tree | fc01065ea93b2b35545bb7bdd6c190a646be7ec6 /tests/codegen | |
| parent | 8575f8f91bbd7dca529d362afc8117db74661c3b (diff) | |
| parent | 59e3e8934e3e50ddb9b9a9ffaa523cbab2260598 (diff) | |
| download | rust-c179a15f7a0a459521022f5aadc10125a33c6efb.tar.gz rust-c179a15f7a0a459521022f5aadc10125a33c6efb.zip | |
Rollup merge of #132612 - compiler-errors:async-trait-bounds, r=lcnr
Gate async fn trait bound modifier on `async_trait_bounds` This PR moves `async Fn()` trait bounds into a new feature gate: `feature(async_trait_bounds)`. The general vibe is that we will most likely stabilize the `feature(async_closure)` *without* the `async Fn()` trait bound modifier, so we need to gate that separately. We're trying to work on the general vision of `async` trait bound modifier general in: https://github.com/rust-lang/rfcs/pull/3710, however that RFC still needs more time for consensus to converge, and we've decided that the value that users get from calling the bound `async Fn()` is *not really* worth blocking landing async closures in general.
Diffstat (limited to 'tests/codegen')
| -rw-r--r-- | tests/codegen/async-closure-debug.rs | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/tests/codegen/async-closure-debug.rs b/tests/codegen/async-closure-debug.rs index 9cb1e623295..644df169a36 100644 --- a/tests/codegen/async-closure-debug.rs +++ b/tests/codegen/async-closure-debug.rs @@ -9,7 +9,7 @@ #![feature(async_closure)] -fn async_closure_test(upvar: &str) -> impl async Fn() + '_ { +fn async_closure_test(upvar: &str) -> impl AsyncFn() + '_ { async move || { let hello = String::from("hello"); println!("{hello}, {upvar}"); |
