aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
* | Merge #302bors[bot]2018-12-244-9/+47
|\ \ | |/ |/| | | | | | | | | | | | | | | | | | | | | | | 302: WIP: Support tracing lsp requests. r=DJMcNab a=DJMcNab EDIT: We need to work out a better way to handle settings before this can be merged. Help wanted TODO: Debug why decorations are sent even when highlightingOn is disabled This makes the log volume so high its impossible to work with anyway. (Continuation of #84 [#99 only disabled using it, not making sure we don't send it]). These logs can be used in https://microsoft.github.io/language-server-protocol/inspector/ Co-authored-by: DJMcNab <[email protected]>
| * Add a very hacky workaround to not trace decorations requestsDJMcNab2018-12-241-1/+25
| |
| * Improve commentDJMcNab2018-12-231-2/+2
| |
| * Undo the previous mistaken change and make publish_decorations optionalDJMcNab2018-12-212-8/+11
| | | | | | | | | | | | | | | | See https://github.com/Microsoft/language-server-protocol/issues/567 for motivations to not require `InitializationOptions` TODO: Check if there are any other protocol extensions which should be disabled if not implemented on the client
| * Disable highlighting if disabledDJMcNab2018-12-201-2/+2
| | | | | | | | | | | | | | | | This isn't working properly because we don't dynamically disable or enable it TODO: work out why highlighting can be enabled mid session. TODO: Improve settings handling
| * Support tracing lsp requests.DJMcNab2018-12-201-0/+11
| | | | | | | | | | | | TODO: Debug why decorations are sent even when highlightingOn is disabled This makes the log volume so high its impossible to work with anyway
* | Merge #310bors[bot]2018-12-221-5/+54
|\ \ | | | | | | | | | | | | | | | | | | | | | 310: When constructing a crate graph, detect and forbid cycles. r=matklad a=gfreezy fixed #300 Co-authored-by: gfreezy <[email protected]>
| * | mark as visited on entry instead of leftgfreezy2018-12-221-2/+2
| | |
| * | not visit the same crateId only oncegfreezy2018-12-221-14/+16
| | |
| * | add #[cfg(test)]gfreezy2018-12-211-1/+2
| | |
| * | rename to dfs_findgfreezy2018-12-211-3/+3
| | |
| * | When constructing a crate graph, detect and forbid cycles.gfreezy2018-12-211-6/+52
| | | | | | | | | | | | fixed #300
* | | Merge #323bors[bot]2018-12-222-5/+12
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 323: workaround salsa/parking-log bug r=matklad a=matklad https://github.com/salsa-rs/salsa/issues/99 https://github.com/Amanieu/parking_lot/issues/101 Co-authored-by: Aleksey Kladov <[email protected]>
| * | | workaround salsa/parking-log bugAleksey Kladov2018-12-222-5/+12
|/ / / | | | | | | | | | | | | https://github.com/salsa-rs/salsa/issues/99 https://github.com/Amanieu/parking_lot/issues/101
* | | Merge #322bors[bot]2018-12-221-13/+17
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 322: Fix analyzer extension fail when there are enabled any VIM extension r=matklad a=max-frai `type` command is allowed only once to be registered and it was built specially for vim mode. So if user has vim extension enabled, rust-analyzer initialization failes on trying to register own `type` handler. Unfortunatelly, there are no nice ways to check if command is already registered so the way is to wrap everything with try/catch and notify user about conflict. Co-authored-by: frai <[email protected]>
| * | | Fix analyzer extension fail when there are enabled any VIM extension.frai2018-12-221-13/+17
|/ / /
* | | less chatty loggingAleksey Kladov2018-12-221-0/+7
| | |
* | | Merge #321bors[bot]2018-12-225-11/+62
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 321: More useful logging r=matklad a=matklad Try not to log *huge* messages, to make logging more useful. Co-authored-by: Aleksey Kladov <[email protected]>
| * | | less verbose debugAleksey Kladov2018-12-222-8/+45
| | | |
| * | | less verbose debug for library dataAleksey Kladov2018-12-222-1/+14
| | | |
| * | | log timesAleksey Kladov2018-12-222-2/+3
|/ / /
* | | Merge #320bors[bot]2018-12-225-27/+39
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 320: completion uses hir scopes r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | | completion uses hir scopesAleksey Kladov2018-12-225-27/+39
|/ / /
* | | Merge #319bors[bot]2018-12-2116-86/+136
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 319: Completion icons r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | | fix snippet iconAleksey Kladov2018-12-211-1/+1
| | | |
| * | | binding iconAleksey Kladov2018-12-213-2/+6
| | | |
| * | | debug pringAleksey Kladov2018-12-211-1/+0
| | | |
| * | | moar iconsAleksey Kladov2018-12-217-7/+34
| | | |
| * | | more iconsAleksey Kladov2018-12-212-2/+15
| | | |
| * | | move completion items to convAleksey Kladov2018-12-215-30/+33
| | | |
| * | | specify completion item kindAleksey Kladov2018-12-214-12/+17
| | | |
| * | | cleanupAleksey Kladov2018-12-214-29/+34
| | | |
| * | | introduce ComletionItemKindAleksey Kladov2018-12-216-34/+28
| | | |
| * | | rename completion kindAleksey Kladov2018-12-211-6/+6
| | | |
* | | | Merge #316bors[bot]2018-12-213-3/+39
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 316: Fix handling of nested self in paths r=matklad a=DJMcNab See https://github.com/rust-analyzer/rust-analyzer/issues/231#issuecomment-442449505. Co-authored-by: DJMcNab <[email protected]>
| * | | | Move the self handling from directly inside the loopDJMcNab2018-12-211-13/+12
| | | | |
| * | | | Fix handling of nested self in pathsDJMcNab2018-12-213-3/+40
| | | | |
* | | | | Merge #318bors[bot]2018-12-212-9/+5
|\ \ \ \ \ | |_|/ / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | 318: Remove a completed and an unactionable todo r=matklad a=DJMcNab Co-authored-by: DJMcNab <[email protected]>
| * | | | Remove TODO on self_hosting_parsingDJMcNab2018-12-211-8/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This improving this code is not a good use of people-time, and this might be the most performant approach nonwithstanding an api for this use case being added to walkdir
| * | | | Remove uneeded todo in lexerDJMcNab2018-12-211-1/+1
|/ / / /
* | | | Merge #315bors[bot]2018-12-219-771/+878
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 315: Split completion into manageable components r=matklad a=matklad The main idea here is to do completion in two phases: * first, we figure out surrounding context * then, we run a series of completers on the given context. Co-authored-by: Aleksey Kladov <[email protected]>
| * | | | cleanupAleksey Kladov2018-12-215-15/+7
| | | | |
| * | | | docsAleksey Kladov2018-12-217-167/+181
| | | | |
| * | | | rename testsAleksey Kladov2018-12-211-8/+8
| | | | |
| * | | | scope-based copmletions on original fileAleksey Kladov2018-12-215-322/+223
| | | | |
| * | | | move path completion to a separate componentAleksey Kladov2018-12-213-44/+127
| | | | |
| * | | | more completion componentsAleksey Kladov2018-12-214-95/+104
| | | | |
| * | | | Start splitting completion into componentsAleksey Kladov2018-12-214-339/+424
| | | | |
| * | | | wipAleksey Kladov2018-12-211-5/+28
| | | | |
* | | | | remove explicit serde_deriveAleksey Kladov2018-12-216-8/+4
| |/ / / |/| | |
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-27 02:08:14 +0000