diff options
| author | Jubilee <workingjubilee@gmail.com> | 2024-11-08 20:46:12 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-11-08 20:46:12 -0800 |
| commit | b59884994104616434d4960753a2df210119f87f (patch) | |
| tree | ace50a5c205cadc69c0c7b328539cddee994c6be /compiler/rustc_llvm/src | |
| parent | 7a4970476e8a9cb387ca48a14a657051769b094f (diff) | |
| parent | cea82ed1626f00930845ea48e3485eae8d44b422 (diff) | |
| download | rust-b59884994104616434d4960753a2df210119f87f.tar.gz rust-b59884994104616434d4960753a2df210119f87f.zip | |
Rollup merge of #132760 - dianne:iter-into-iter, r=lcnr
Don't suggest `.into_iter()` on iterators This makes the the suggestion to call `.into_iter()` only consider unsatisfied `Iterator` bounds for the receiver type itself. That way, it ignores predicates generated by trying to auto-ref the receiver (the result of which usually won't implement `Iterator`). Fixes #127511 Unfortunately, the error in that case is still confusing: it labels `Iterator` as an unsatisfied bound because `&impl Iterator: Iterator` can't be satisfied, despite that not being required or helpful. I'd like to handle that in a separate PR. ~~I'm hoping fixing #124802 will fix it too.~~ It doesn't look connected to that issue. Still, I think it'd be clearest to visually distinguish unsatisfied predicates from different attempts at `pick_method`; I'll make a PR for that soon.
Diffstat (limited to 'compiler/rustc_llvm/src')
0 files changed, 0 insertions, 0 deletions
