commit | a670ff888437f4b6a3d24cc2996e9f969a87cbae | [log] [tgz] |
---|---|---|
author | bors <bors@rust-lang.org> | Sun Aug 21 12:21:33 2022 +0000 |
committer | bors <bors@rust-lang.org> | Sun Aug 21 12:21:33 2022 +0000 |
tree | a88648337e105bbe8320f141f5d65277ded7ac8a | |
parent | e1623635aa7281f73f96d4f2098e056641797eb0 [diff] | |
parent | dd22aa48bab8ff47025d806df481cad412b2747f [diff] |
Auto merge of #13074 - lowr:fix/method-resolution-with-impl-predicate, r=lowr Consider bounds on inherent impl in method resolution There are three type-related things we should consider in method resolution: `Self` type, receiver type, and impl bounds. While we check the first two and impl bounds on trait impls, we've been ignoring the impl bounds on inherent impls. With this patch rust-analyzer now takes them into account and is able to select the appropriate inherent method. Resolves #5441 Resolves #12308
rust-analyzer is a modular compiler frontend for the Rust language. It is a part of a larger rls-2.0 effort to create excellent IDE support for Rust.
https://rust-analyzer.github.io/manual.html#installation
If you want to contribute to rust-analyzer or are just curious about how things work under the hood, check the ./docs/dev folder.
If you want to use rust-analyzer's language server with your editor of choice, check the manual folder. It also contains some tips & tricks to help you be more productive when using rust-analyzer.
See the corresponding sections of the manual.
For usage and troubleshooting requests, please use “IDEs and Editors” category of the Rust forum:
https://users.rust-lang.org/c/ide/14
For questions about development and implementation, join rust-analyzer working group on Zulip:
https://rust-lang.zulipchat.com/#narrow/stream/185405-t-compiler.2Frust-analyzer
rust-analyzer is primarily distributed under the terms of both the MIT license and the Apache License (Version 2.0).
See LICENSE-APACHE and LICENSE-MIT for details.