aboutsummaryrefslogtreecommitdiff
path: root/Cargo.lock
Commit message (Collapse)AuthorAgeFilesLines
...
* Use itertoolsJonas Schievink2020-12-101-0/+1
|
* Make config.rs a single source of truth for configuration.Aleksey Kladov2020-12-081-0/+1
| | | | | | | | | | | | | | | | | Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
* Update expect-test and remove outdated licensekjeremy2020-12-071-4/+4
|
* cargo updatekjeremy2020-12-071-25/+15
|
* Retain types of proc macros and allow attr. macrosJonas Schievink2020-12-071-0/+1
|
* Upgrade ChalkFlorian Diebold2020-12-071-8/+8
| | | | | | | Also make overflow depth and max type size configurable through env variables. This can be helpful at least for debugging. Fixes #6628.
* cargo update: bump libloading to fix a double-freekjeremy2020-12-031-4/+4
|
* Bump mio for safety goodnesskjeremy2020-12-021-2/+2
|
* Fix OptionalVersionedTextDocumentIdentifier typekjeremy2020-12-011-2/+2
| | | | Fixes #6654
* bump lexerkjeremy2020-11-301-2/+2
|
* cargo updatekjeremy2020-11-301-20/+19
|
* Move the helpers into ide_dbKirill Bulatov2020-11-281-17/+1
|
* Extract the import code into the shared moduleKirill Bulatov2020-11-271-1/+17
|
* Profile completions betterKirill Bulatov2020-11-271-0/+1
|
* cargo updatekjeremy2020-11-241-15/+15
|
* New lsp-types to fix versioningkjeremy2020-11-241-2/+2
| | | | Fixes #6603
* cargo updatekjeremy2020-11-191-16/+16
|
*-. Merge #6577 #6579 #6581bors[bot]2020-11-171-10/+19
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 6577: fix typos in syntax.md r=matklad a=jakobhellermann 6579: cargo update and add new license r=matklad a=kjeremy 6581: Use vscode-languageclient 7.0.0-next.14 r=matklad a=kjeremy Co-authored-by: Jakob Hellermann <[email protected]> Co-authored-by: kjeremy <[email protected]>
| | * cargo update and add new licensekjeremy2020-11-171-10/+19
| |/
* | Merge #6553bors[bot]2020-11-171-0/+1
|\ \ | |/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 6553: Auto imports in completion r=matklad a=SomeoneToIgnore ![completion](https://user-images.githubusercontent.com/2690773/99155339-ae4fb380-26bf-11eb-805a-655b1706ce70.gif) Closes https://github.com/rust-analyzer/rust-analyzer/issues/1062 but does not handle the completion order, since it's a separate task for https://github.com/rust-analyzer/rust-analyzer/issues/4922 , https://github.com/rust-analyzer/rust-analyzer/issues/4922 and maybe something else. 2 quirks in the current implementation: * traits are not auto imported during method completion If I understand the current situation right, we cannot search for traits by a **part** of a method name, we need a full name with correct case to get a trait for it. * VSCode (?) autocompletion is not as rigid as in Intellij Rust as you can notice on the animation. Intellij is able to refresh the completions on every new symbol added, yet VS Code does not query the completions on every symbol for me. With a few debug prints placed in RA, I've observed the following behaviour: after the first set of completion suggestions is received, next symbol input does not trigger a server request, if the completions contain this symbol. When more symbols added, the existing completion suggestions are filtered out until none are left and only then, on the next symbol it queries for completions. It seems like the only alternative to get an updated set of results is to manually retrigger it with Esc and Ctrl + Space. Despite the eerie latter bullet, the completion seems to work pretty fine and fast nontheless, but if you have any ideas on how to make it more smooth, I'll gladly try it out. Co-authored-by: Kirill Bulatov <[email protected]>
| * Omit modules during autocompletionKirill Bulatov2020-11-161-54/+105
| |
| * Add imports in auto completionKirill Bulatov2020-11-161-105/+55
| |
* | Latest LSP 3.16 protocolkjeremy2020-11-161-4/+4
|/ | | | Pulls in https://github.com/gluon-lang/lsp-types/pull/186
* add suggestion ..Default::default() for remaining struct fields in a ↵Benjamin Coenen2020-11-131-0/+1
| | | | | | constructor #6492 Signed-off-by: Benjamin Coenen <[email protected]>
* Update crateskjeremy2020-11-111-11/+22
|
* Do not use yanked once_cellkjeremy2020-11-111-2/+2
|
* Replace RacyFlag with OnceCellAleksey Kladov2020-11-111-2/+3
|
* cargo updatekjeremy2020-11-051-6/+6
|
* Bump chalk and lexerkjeremy2020-11-021-10/+10
|
* Update cratesAleksey Kladov2020-11-021-7/+7
| | | | This is to bust the caches
* cargo updateJeremy Kolb2020-10-311-18/+18
|
* Upgrade Chalk to 0.36Florian Diebold2020-10-301-8/+8
| | | | Quite a few changes, because Chalk got rid of the `ApplicationTy` nesting.
* cargo updatekjeremy2020-10-281-7/+7
|
* Latest proposed LSP 3.16.0kjeremy2020-10-261-2/+2
| | | | Needs: https://github.com/gluon-lang/lsp-types/pull/183
* Add tracing to main rust-analyzer binaryFlorian Diebold2020-10-251-0/+3
|
*-. Merge #6331 #6342bors[bot]2020-10-241-21/+1
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 6331: correct hover text for items with doc attribute with raw strings r=matklad a=JoshMcguigan Fixes #6300 by improving the handling of raw string literals in attribute style doc comments. This still has a bug where it could consume too many `"` at the start or end of the comment text, just as the original code had. Not sure if we want to fix that as part of this PR or not? If so, I think I'd prefer to add a unit test for either the `as_simple_key_value` function (I'm not exactly sure where this would belong / how to set this up) or create a `fn(&SmolStr) -> &SmolStr` to unit test by factoring out the `trim` operations from `as_simple_key_value`. Thoughts on this? 6342: Shorter dependency chain r=matklad a=popzxc Continuing implementing suggestions from the `Completion refactoring` zulip thread. This PR does the following: - Removes dependency of `completions` on `assists` by moving required functionality into `ide_db`. - Moves completely `call_info` crate into `ide_db` as it looks like it fits perfect there. - Adds a bunch of new tests and docs. - Adds the re-export of `base_db` to the `ide_db` and removes direct dependency on `base_db` from other crates. The last point is controversial, I guess, but I noticed that in places where `ide_db` is used, `base_db` is also *always* used. Thus I think the dependency on the `base_db` is implied by the fact of `ide_db` interfaces, and thus it makes sense to just provide `base_db` out of the box. Co-authored-by: Josh Mcguigan <[email protected]> Co-authored-by: Igor Aleksanov <[email protected]>
| | * Re-export base_db from ide_dbIgor Aleksanov2020-10-241-4/+0
| | |
| | * Make call_info a part of ide_dbIgor Aleksanov2020-10-241-16/+1
| | |
| | * Remove dependency on 'assists' from 'completion' crateIgor Aleksanov2020-10-241-1/+0
| | |
* | | Bump chalkLaurențiu Nicola2020-10-241-8/+8
| | |
* | | Bump rustc_lexerLaurențiu Nicola2020-10-241-2/+2
| | |
* | | Bump depsLaurențiu Nicola2020-10-241-36/+86
| |/ |/|
| |
| \
*-. \ Merge #6251 #6310bors[bot]2020-10-231-0/+1
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 6251: Semantic Highlight: Add Callable modifier for variables r=matklad a=GrayJack This PR added the `HighlightModifier::Callable` variant and assigned it to variables and parameters that are fn pointers, closures and implements FnOnce trait. This allows to colorize these variables/parameters when used in call expression. 6310: Rewrite algo::diff to support insertion and deletion r=matklad a=Veykril This in turn also makes `algo::diff` generate finer diffs(maybe even minimal diffs?) as insertions and deletions aren't always represented as as replacements of parent nodes now. Required for #6287 to go on. Co-authored-by: GrayJack <[email protected]> Co-authored-by: Lukas Wirth <[email protected]>
| | * | Rewrite algo::diff to support insertion and deletionLukas Wirth2020-10-221-0/+1
| | |/
* | | Merge #6324bors[bot]2020-10-231-0/+1
|\ \ \ | |_|/ |/| | | | | | | | | | | | | | | | | | | | 6324: Improve #[cfg] diagnostics r=jonas-schievink a=jonas-schievink Unfortunately I ran into https://github.com/rust-analyzer/rust-analyzer/issues/4058 while testing this on https://github.com/nrf-rs/nrf-hal/, so I didn't see much of it in action yet, but it does seem to work. Co-authored-by: Jonas Schievink <[email protected]> Co-authored-by: Jonas Schievink <[email protected]>
| * | Implement DNF-based `#[cfg]` introspectionJonas Schievink2020-10-221-0/+1
| | |
* | | Update cratesJeremy Kolb2020-10-201-8/+26
|/ / | | | | | | This brings in a number of new dependencies though.
* | :arrow_up: cratesAleksey Kladov2020-10-191-6/+6
| |
* | Extract call_info and completion into separate cratesIgor Aleksanov2020-10-181-0/+36
| |
* | update depsAleksey Kladov2020-10-181-4/+4
| |
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-18 05:40:29 +0000