aboutsummaryrefslogtreecommitdiff
path: root/crates/ra_hir/src/ty/method_resolution.rs
Commit message (Collapse)AuthorAgeFilesLines
* Decouple moreAleksey Kladov2019-11-271-4/+3
|
* DecoupleAleksey Kladov2019-11-271-5/+5
|
* DecoupleAleksey Kladov2019-11-271-1/+1
|
* CleanupAleksey Kladov2019-11-261-62/+39
|
* DecoupleAleksey Kladov2019-11-261-23/+23
|
* Use TraitId in TraitRefAleksey Kladov2019-11-261-10/+8
|
* Store names in TraitDataAleksey Kladov2019-11-261-3/+3
|
* Detangle ty from traits a bitAleksey Kladov2019-11-261-2/+3
|
* id-ify impls_in_crate_queryAleksey Kladov2019-11-261-46/+55
|
* Id-ify Ty::AdtAleksey Kladov2019-11-261-2/+4
|
* Use GenericDefIdMoreAleksey Kladov2019-11-251-1/+1
|
* Remove Resolver from autoderefAleksey Kladov2019-11-251-5/+6
| | | | | Resolver holds onto too much context, including local scopes. Let's try to pass in only what is necessary -- the trait environment.
* Move lang_items to hir_defAleksey Kladov2019-11-231-19/+28
|
* Remove TraitData from APIAleksey Kladov2019-11-221-1/+1
|
* Move FunctionData to hir_defAleksey Kladov2019-11-221-3/+3
|
* Move resolver to hir_defAleksey Kladov2019-11-211-1/+1
|
* DecoupleAleksey Kladov2019-11-211-5/+10
|
* Decouple ResolverAleksey Kladov2019-11-211-1/+3
|
* Move traits to hir_defAleksey Kladov2019-11-201-3/+3
|
* Use Chalk's dyn/impl trait supportFlorian Diebold2019-11-161-5/+1
|
* Remove old impls infrastructureAleksey Kladov2019-11-151-58/+22
|
* Reduce duplication between uncertain floats & intsAleksey Kladov2019-11-131-6/+5
|
* Various review fixesFlorian Diebold2019-11-011-6/+5
|
* Add some doc commentsFlorian Diebold2019-11-011-0/+6
|
* Complete trait assoc itemsFlorian Diebold2019-11-011-1/+1
|
* Refactor a bitFlorian Diebold2019-11-011-36/+25
|
* Don't do autoderef for path resolutionFlorian Diebold2019-11-011-18/+39
|
* Refactor to unify with method resolutionFlorian Diebold2019-11-011-23/+67
|
* remove forward pointer for type_refAleksey Kladov2019-10-301-2/+1
|
* introduce ra_hir_defAleksey Kladov2019-10-301-6/+6
|
* Add SubstsBuilderFlorian Diebold2019-09-261-13/+5
| | | | + further refactoring.
* Merge #1906bors[bot]2019-09-251-2/+5
|\ | | | | | | | | | | | | | | 1906: Add missing lang-items to `def_crates` r=matklad a=sinkuu Co-authored-by: Shotaro Yamada <[email protected]>
| * Add missing lang-items to `def_crates`Shotaro Yamada2019-09-251-2/+5
| |
* | Remove redundant clone()Shotaro Yamada2019-09-251-1/+1
|/
* Remove TraitItem and ImplItem in favor of AssocItemFlorian Diebold2019-09-171-6/+5
|
* cleanup hir db importsAleksey Kladov2019-09-081-1/+2
|
* Use traits from where clauses for method resolutionFlorian Diebold2019-09-071-1/+7
| | | | | E.g. if we have `T: some::Trait`, we can call methods from that trait without it needing to be in scope.
* Handle impl/dyn Trait in method resolutionFlorian Diebold2019-08-221-2/+14
| | | | | | | | | | | | | When we have one of these, the `Trait` doesn't need to be in scope to call its methods. So we need to consider this when looking for method candidates. (Actually I think the same is true when we have a bound `T: some::Trait`, but we don't handle that yet). At the same time, since Chalk doesn't handle these types yet, add a small hack to skip Chalk in method resolution and just consider `impl Trait: Trait` always true. This is enough to e.g. get completions for `impl Trait`, but since we don't do any unification we won't infer the return type of e.g. `impl Into<i64>::into()`.
* show inherent and trait impls of structs and enumsEkaterina Babshukova2019-08-161-0/+9
|
* do fixup: remove unused importEvgenii P2019-08-021-1/+1
|
* Relax trait solving more for completionEvgenii P2019-08-021-7/+1
|
* rustfmtEvgenii P2019-08-021-3/+9
|
* Implement completion for the .await syntaxEvgenii P2019-08-021-1/+15
|
* Some renamings for clarityFlorian Diebold2019-07-141-3/+3
|
* Merge #1515bors[bot]2019-07-091-9/+12
|\ | | | | | | | | | | | | | | | | | | | | | | 1515: Trait environment r=matklad a=flodiebold This adds the environment, i.e. the set of `where` clauses in scope, when solving trait goals. That means that e.g. in ```rust fn foo<T: SomeTrait>(t: T) {} ``` , we are able to complete methods of `SomeTrait` on the `t`. This affects the trait APIs quite a bit (since every method that needs to be able to solve for some trait needs to get this environment somehow), so I thought I'd do it rather sooner than later ;) Co-authored-by: Florian Diebold <[email protected]>
| * Unify `normalize` and `implements` to simplify codeFlorian Diebold2019-07-081-8/+8
| |
| * Start handling environment in trait resolutionFlorian Diebold2019-07-081-3/+4
| | | | | | | | | | I.e. if we are inside a function with some where clauses, we assume these where clauses hold.
| * Refactor a bit & introduce Environment structFlorian Diebold2019-07-081-4/+6
| |
* | Look for the fXX_runtime lang items during method resolution.Marco Groppo2019-07-081-4/+6
|/
* Moved module resolution test in mods.rsAlexander Andreev2019-07-071-1/+1
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-03 00:18:37 +0000