diff options
| author | bors[bot] <bors[bot]@users.noreply.github.com> | 2019-02-22 19:58:22 +0000 |
|---|---|---|
| committer | bors[bot] <bors[bot]@users.noreply.github.com> | 2019-02-22 19:58:22 +0000 |
| commit | 3d8a0982a12f3aa4b8c193a841f864b15c3cb66e (patch) | |
| tree | e20ae00628cc28417e22621f583ba6988677ffcd /crates/ra_syntax/tests/data/lexer/0008_byte_strings.rs | |
| parent | bb665a70627cbc2f4fb930fefb04899941b6afa6 (diff) | |
| parent | 247d1c17b385ff8a8c1dda2e899495146b643b98 (diff) | |
Merge #866
866: Implement basic support for Associated Methods r=flodiebold a=vipentti
This is my attempt at learning to understand how the type inference works by adding basic support for associated methods. Currently it does not resolve associated types or constants.
The basic idea is that `Resolver::resolve_path` returns a new `PathResult` type, which has two variants, `FullyResolved` and `PartiallyResolved`, fully resolved matches the previous behavior, where as `PartiallyResolved` contains the `PerNs<Resolution` in addition to a `segment_index` which contains the index of the segment which we failed to resolve. This index can then be used to continue inference in `infer_path_expr` using the `Type` we managed to resolve.
This changes some of the previous apis, so looking for feedback and suggestions.
This should enable fixing #832
Co-authored-by: Ville Penttinen <[email protected]>
Diffstat (limited to 'crates/ra_syntax/tests/data/lexer/0008_byte_strings.rs')
0 files changed, 0 insertions, 0 deletions