forked from rust-lang/rust
-
Notifications
You must be signed in to change notification settings - Fork 1
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#57981 - Zoxc:fix-57979, r=nikomatsakis
Fix rust-lang#57730 cc rust-lang#57730 r? @cramertj
- Loading branch information
Showing
3 changed files
with
60 additions
and
1 deletion.
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,42 @@ | ||
// Regression test for #57979. This situation is meant to be an error. | ||
// As noted in the issue thread, we decided to forbid nested impl | ||
// trait of this kind: | ||
// | ||
// ```rust | ||
// fn foo() -> impl Foo<impl Bar> { .. } | ||
// ``` | ||
// | ||
// Basically there are two hidden variables here, let's call them `X` | ||
// and `Y`, and we must prove that: | ||
// | ||
// ``` | ||
// X: Foo<Y> | ||
// Y: Bar | ||
// ``` | ||
// | ||
// However, the user is only giving us the return type `X`. It's true | ||
// that in some cases, we can infer `Y` from `X`, because `X` only | ||
// implements `Foo` for one type (and indeed the compiler does | ||
// inference of this kind), but I do recall that we intended to forbid | ||
// this -- in part because such inference is fragile, and there is not | ||
// necessarily a way for the user to be more explicit should the | ||
// inference fail (so you could get stuck with no way to port your | ||
// code forward if, for example, more impls are added to an existing | ||
// type). | ||
// | ||
// The same seems to apply in this situation. Here there are three impl traits, so we have | ||
// | ||
// ``` | ||
// X: IntoIterator<Item = Y> | ||
// Y: Borrow<Data<Z>> | ||
// Z: AsRef<[u8]> | ||
// ``` | ||
|
||
use std::borrow::Borrow; | ||
|
||
pub struct Data<TBody>(TBody); | ||
|
||
pub fn collect(_: impl IntoIterator<Item = impl Borrow<Data<impl AsRef<[u8]>>>>) { | ||
//~^ ERROR | ||
unimplemented!() | ||
} |
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,17 @@ | ||
error[E0666]: nested `impl Trait` is not allowed | ||
--> $DIR/issue-57979.rs:39:61 | ||
| | ||
LL | pub fn collect(_: impl IntoIterator<Item = impl Borrow<Data<impl AsRef<[u8]>>>>) { | ||
| -----------------^^^^^^^^^^^^^^^^-- | ||
| | | | ||
| | nested `impl Trait` here | ||
| outer `impl Trait` | ||
|
||
error[E0601]: `main` function not found in crate `issue_57979` | ||
| | ||
= note: consider adding a `main` function to `$DIR/issue-57979.rs` | ||
|
||
error: aborting due to 2 previous errors | ||
|
||
Some errors occurred: E0601, E0666. | ||
For more information about an error, try `rustc --explain E0601`. |