We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IntoIterator
When having multiple IntoIterator bounds on a function - even if completely unrelated - type inference breaks down.
rust-analyzer version: nightly-2024-10-21
nightly-2024-10-21
rustc version: rustc 1.84.0-nightly (662180b34 2024-10-20)
rustc 1.84.0-nightly (662180b34 2024-10-20)
editor or extension: Zed on mac
code snippet to reproduce:
fn x<A, B>(a: A) where A: IntoIterator<Item = u8>, B: IntoIterator<Item = u16>, { for u in a {} }
when we change B to any other bound, like: B: Iterator<Item = u16> the type inference will work for a:
B
B: Iterator<Item = u16>
a
fn x<A, B>(a: A) where A: IntoIterator<Item = u8>, B: Iterator<Item = u16>, { for u in a {} }
The text was updated successfully, but these errors were encountered:
Duplicate of #10653.
Sorry, something went wrong.
No branches or pull requests
When having multiple
IntoIterator
bounds on a function - even if completely unrelated - type inference breaks down.rust-analyzer version:
nightly-2024-10-21
rustc version:
rustc 1.84.0-nightly (662180b34 2024-10-20)
editor or extension: Zed on mac
code snippet to reproduce:
when we change
B
to any other bound, like:B: Iterator<Item = u16>
the type inference will work fora
:The text was updated successfully, but these errors were encountered: