aboutsummaryrefslogtreecommitdiff
path: root/crates/parser/Cargo.toml
diff options
context:
space:
mode:
authorbors[bot] <26634292+bors[bot]@users.noreply.github.com>2021-01-05 12:04:35 +0000
committerGitHub <[email protected]>2021-01-05 12:04:35 +0000
commitd7013a5934af1e2aaa60dcf19b1b6bb529594565 (patch)
treed9383f5f08d2beed056aa013da3a21f76002f06c /crates/parser/Cargo.toml
parent5c10f2f705d6757b9821387a5be759789b7ee480 (diff)
parent543e950e305aa7bd7e0b185753752d0561c70459 (diff)
Merge #7140
7140: Store trait associated items in fst r=matklad a=SomeoneToIgnore Store imported traits' associated function/methods and constants into `ImportMap.fst` and pefrorm the imports search on them. This is a first step towards trait autoimport during completion functionality, the way I see it, after this PR, only a few major things are left to be done: * store all traits' assoc items into fst, not only the ones in scope, as we do now. Any code pointers on how to do this are welcome 😄 * adjust a few modules in completions crate (`dot.rs`, `qualified_path.rs` at least) to query the import map, reusing the `import_assets` logic heavily == With the current import and autoimport implementations, it looks like for a single query, we're either interested in either associated items lookup or in all other `fst` contents lookup, but never both simultaneously. I would rather not split `fst` in two but add another `Query` parameter to separate those, but let me know if you have any ideas. Co-authored-by: Kirill Bulatov <[email protected]>
Diffstat (limited to 'crates/parser/Cargo.toml')
0 files changed, 0 insertions, 0 deletions