forked from rust-lang/rust
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Rollup merge of rust-lang#80211 - wabain:async-fn-trait-bound-suggest…
…ion, r=petrochenkov Handle desugaring in impl trait bound suggestion Fixes rust-lang#79843. When an associated type of a generic function parameter needs extra bounds, the diagnostics may suggest replacing an `impl Trait` with a named type parameter so that it can be referenced in the where clause. On stable and nightly, the suggestion can be malformed, for instance transforming: ```rust async fn run(_: &(), foo: impl Foo) -> std::io::Result<()> ``` Into: ```rust async fn run(_: &, F: Foo(), foo: F) -> std::io::Result<()> where <F as Foo>::Bar: Send ^^^^^^^^ ^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^ ``` Where we want something like: ```rust async fn run<F: Foo>(_: &(), foo: F) -> std::io::Result<()> where <F as Foo>::Bar: Send ^^^^^^^^ ^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^ ``` The problem is that the elided lifetime of `&()` is added as a generic parameter when desugaring the async fn; the suggestion code sees this as an existing generic parameter and tries to use its span as an anchor to inject `F` into the parameter list. There doesn't seem to be an entirely principled way to check which generic parameters in the HIR were explicitly named in the source, so this commit changes the heuristics when generating the suggestion to only consider type parameters whose spans are contained within the span of the `Generics` when determining how to insert an additional type parameter into the declaration. (And to be safe it also excludes parameters whose spans are marked as originating from desugaring, although that doesn't seem to handle this elided lifetime.)
- Loading branch information
Showing
5 changed files
with
95 additions
and
13 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
32 changes: 32 additions & 0 deletions
32
src/test/ui/suggestions/issue-79843-impl-trait-with-missing-bounds-on-async-fn.rs
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,32 @@ | ||
// Regression test: if we suggest replacing an `impl Trait` argument to an async | ||
// fn with a named type parameter in order to add bounds, the suggested function | ||
// signature should be well-formed. | ||
// | ||
// edition:2018 | ||
|
||
trait Foo { | ||
type Bar; | ||
fn bar(&self) -> Self::Bar; | ||
} | ||
|
||
async fn run(_: &(), foo: impl Foo) -> std::io::Result<()> { | ||
let bar = foo.bar(); | ||
assert_is_send(&bar); | ||
//~^ ERROR: `<impl Foo as Foo>::Bar` cannot be sent between threads safely | ||
|
||
Ok(()) | ||
} | ||
|
||
// Test our handling of cases where there is a generic parameter list in the | ||
// source, but only synthetic generic parameters | ||
async fn run2< >(_: &(), foo: impl Foo) -> std::io::Result<()> { | ||
let bar = foo.bar(); | ||
assert_is_send(&bar); | ||
//~^ ERROR: `<impl Foo as Foo>::Bar` cannot be sent between threads safely | ||
|
||
Ok(()) | ||
} | ||
|
||
fn assert_is_send<T: Send>(_: &T) {} | ||
|
||
fn main() {} |
33 changes: 33 additions & 0 deletions
33
src/test/ui/suggestions/issue-79843-impl-trait-with-missing-bounds-on-async-fn.stderr
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,33 @@ | ||
error[E0277]: `<impl Foo as Foo>::Bar` cannot be sent between threads safely | ||
--> $DIR/issue-79843-impl-trait-with-missing-bounds-on-async-fn.rs:14:20 | ||
| | ||
LL | assert_is_send(&bar); | ||
| ^^^^ `<impl Foo as Foo>::Bar` cannot be sent between threads safely | ||
... | ||
LL | fn assert_is_send<T: Send>(_: &T) {} | ||
| ---- required by this bound in `assert_is_send` | ||
| | ||
= help: the trait `Send` is not implemented for `<impl Foo as Foo>::Bar` | ||
help: introduce a type parameter with a trait bound instead of using `impl Trait` | ||
| | ||
LL | async fn run<F: Foo>(_: &(), foo: F) -> std::io::Result<()> where <F as Foo>::Bar: Send { | ||
| ^^^^^^^^ ^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
|
||
error[E0277]: `<impl Foo as Foo>::Bar` cannot be sent between threads safely | ||
--> $DIR/issue-79843-impl-trait-with-missing-bounds-on-async-fn.rs:24:20 | ||
| | ||
LL | assert_is_send(&bar); | ||
| ^^^^ `<impl Foo as Foo>::Bar` cannot be sent between threads safely | ||
... | ||
LL | fn assert_is_send<T: Send>(_: &T) {} | ||
| ---- required by this bound in `assert_is_send` | ||
| | ||
= help: the trait `Send` is not implemented for `<impl Foo as Foo>::Bar` | ||
help: introduce a type parameter with a trait bound instead of using `impl Trait` | ||
| | ||
LL | async fn run2<F: Foo>(_: &(), foo: F) -> std::io::Result<()> where <F as Foo>::Bar: Send { | ||
| ^^^^^^^^ ^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
|
||
error: aborting due to 2 previous errors | ||
|
||
For more information about this error, try `rustc --explain E0277`. |