diff options
| author | bors <bors@rust-lang.org> | 2024-05-22 20:38:28 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2024-05-22 20:38:28 +0000 |
| commit | ac2708a347508e5b1315e342eb164b7356105ace (patch) | |
| tree | dac884011d3b8cb08ffd38a21c51d0b6961a2a91 /tests/rustdoc-js-std/parser-paths.js | |
| parent | 0916e72a347f3bb0fb8de70b94a057e3e6f389fc (diff) | |
| parent | f2c3ef77b1976eee67ae88ac12cbd1eb4e2da398 (diff) | |
| download | rust-ac2708a347508e5b1315e342eb164b7356105ace.tar.gz rust-ac2708a347508e5b1315e342eb164b7356105ace.zip | |
Auto merge of #17270 - davidbarsky:david/fix-completions-from-associated-types, r=Veykril
fix: ensure implied bounds from associated types are considered in autocomplete closes: #16989 rust-analyzer needs to consider implied bounds from associated types in order to get all methods suggestions people expect. A pretty easy way to do that is to keep the `candidate_trait_id`'s receiver if it matches `TyFingerprint::Unnameable`. When benchmarking this change, I didn't notice a meaningful difference in autocomplete latency. (`TyFingerprint::Unnameable` corresponds to `TyKind::AssociatedType`, `TyKind::OpaqueType`, `TyKind::FnDef`, `TyKind::Closure`, `TyKind::Coroutine`, and `TyKind::CoroutineWitness`.)
Diffstat (limited to 'tests/rustdoc-js-std/parser-paths.js')
0 files changed, 0 insertions, 0 deletions
