aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Merge #416bors[bot]2019-01-0312-214/+286
|\ | | | | | | | | | | | | | | 416: assist-builder r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * fix the testAleksey Kladov2019-01-032-6/+1
| |
| * more enterprisey assists APIAleksey Kladov2019-01-0311-210/+287
| |
* | Merge #415bors[bot]2019-01-034-78/+61
|\ \ | |/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | | 415: use LSP file system operations r=matklad a=vemoo implements #131 I've replaced `source_file_edits` and `file_system_edits` with `workspace_edit` because [`WorkspacEdit`](https://docs.rs/languageserver-types/0.53.1/languageserver_types/struct.WorkspaceEdit.html) can represent both. I only use `document_changes` because `changes` cannot represent file system operations. But if the client doesn't have the `workspace.workspaceEdit.resourceOperations` capability `WorkspaceEdit` cannot replace the current `FileSystemEdit`. Can we assume that the client will support it? I also adapted the extension code to make use of the new response type, but only for vscode, i don't know if changes have to be made for the emacs part. Co-authored-by: Bernardo <[email protected]>
| * fix testsBernardo2019-01-031-9/+14
| |
| * use lsp WorkspaceEdit instead of custom source_file_edits and file_system_editsBernardo2019-01-033-69/+47
|/
* Merge #413bors[bot]2019-01-0312-428/+573
|\ | | | | | | | | | | | | | | 413: add visibility owner, refactor assists r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * split assists over several filesAleksey Kladov2019-01-038-403/+488
| |
| * rename code-actions -> assistsAleksey Kladov2019-01-033-8/+8
| |
| * visibility ownerAleksey Kladov2019-01-033-4/+64
|/
* Merge #412bors[bot]2019-01-032-1/+27
|\ | | | | | | | | | | | | | | 412: vec-macro r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * hardcode vec macroAleksey Kladov2019-01-032-1/+27
|/
* Merge #409bors[bot]2019-01-031-0/+79
|\ | | | | | | | | | | | | | | 409: Add Analysis#teype_of test r=matklad a=h-michael Co-authored-by: Hirokazu Hata <[email protected]>
| * Deive type_of test from testsHirokazu Hata2019-01-032-17/+80
| |
| * Remove unnecessary mock functionsHirokazu Hata2019-01-031-27/+1
| |
| * Add Analysis#teype_of testHirokazu Hata2019-01-032-2/+44
| |
* | Merge #410bors[bot]2019-01-036-171/+221
|\ \ | | | | | | | | | | | | | | | | | | | | | 410: Detangle symbols r=matklad a=matklad Previously, we used `FileSymbol` both to represent bytes which are stored in the index and as an API of `ra_analysis`. Mixing internal storage format and an API is not a really bright idea, so we introduce `NavigationTarget` to handle API part. Co-authored-by: Aleksey Kladov <[email protected]>
| * | docsAleksey Kladov2019-01-032-3/+33
| | |
| * | use LocalPtr in navigation targetAleksey Kladov2019-01-034-7/+13
| | |
| * | use LocalSyntaxPtr for file symbolAleksey Kladov2019-01-033-53/+49
| | |
| * | move some logic to navigation targetAleksey Kladov2019-01-033-113/+127
| | |
| * | add kind to LocalSyntaxPtrAleksey Kladov2019-01-031-0/+4
|/ /
* / explain that completion shouldn't do filteringAleksey Kladov2019-01-031-1/+15
|/
* Merge #408bors[bot]2019-01-021-14/+50
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 408: vscode problem matcher improvements r=matklad a=vemoo The problem matcher wasn't working properly and looking at the rustc errors i realized it could be simplified. I also added a new problem matcher that can be used with https://github.com/passcod/cargo-watch to get the errors in the editor on save. To use it one can create a tasks.json file with: ```json { "version": "2.0.0", "tasks": [ { "type": "shell", "label": "cargo watch", "command": "cargo", "isBackground": true, "args": [ "watch", "-c" ], "problemMatcher": [ "$rustc-watch" ] } ] } ``` I initially implemented it like this: https://github.com/rust-analyzer/rust-analyzer/commit/cff9f62d321a90c45e622f5304e60a248cbcf4f2 but i think there's a bug in vscode so i worked around it by copying the pattern for both problem matchers. The first commit can be used if https://github.com/Microsoft/vscode/pull/65840 is merged. Co-authored-by: Bernardo <[email protected]>
| * named multiline problem patterns are not parsed properly in vscode at the momentBernardo2019-01-011-2/+29
| |
| * fix regex and add rustc-watch problem matcherBernardo2019-01-011-23/+32
| |
* | Merge #407bors[bot]2019-01-027-124/+65
|\ \ | | | | | | | | | | | | | | | | | | | | | 407: run r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | simplify runnablesAleksey Kladov2019-01-027-124/+65
| | |
* | | Merge #406bors[bot]2019-01-024-218/+203
|\| | | | | | | | | | | | | | | | | | | | | | | 406: Simplify r=matklad a=matklad Get rid of `AnalysisImpl` wrapper around salsa database. It was useful before we migrated by salsa, but it's long have been just a useless boilerplate. Co-authored-by: Aleksey Kladov <[email protected]>
| * | fix compilationAleksey Kladov2019-01-022-2/+2
| | |
| * | doctringsAleksey Kladov2019-01-021-28/+62
| | |
| * | get rid of AnalysisImplAleksey Kladov2019-01-022-101/+80
| | |
| * | remove AnalysisHostImplAleksey Kladov2019-01-022-45/+26
| | |
| * | remove some methods from analysis implAleksey Kladov2019-01-022-22/+13
| | |
| * | move world-symbols to file_symbolsAleksey Kladov2019-01-023-42/+42
| | |
* | | Merge #405bors[bot]2019-01-022-5/+21
|\ \ \ | |/ / |/| | | | | | | | | | | | | | | | | 405: extend selection inside a string literal should select a word first r=matklad a=gfreezy fixed #402 Co-authored-by: gfreezy <[email protected]>
| * | extend selection inside a string literal should select a word firstgfreezy2019-01-022-5/+21
|/ /
* | Merge #404bors[bot]2019-01-029-298/+329
|\ \ | | | | | | | | | | | | | | | | | | | | | 404: Move FileSymbol to ra_analysis r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | fix testsAleksey Kladov2019-01-021-5/+5
| | |
| * | make FileSymbol privateAleksey Kladov2019-01-022-8/+7
| | |
| * | use navigation target in APIAleksey Kladov2019-01-024-26/+44
| | |
| * | introduce navigation targetAleksey Kladov2019-01-023-13/+28
| | |
| * | move symbols to ra_analysisAleksey Kladov2019-01-026-256/+255
| |/
* | Merge #403bors[bot]2019-01-0222-344/+778
|\ \ | |/ |/| | | | | | | | | | | 403: initial support for macros r=matklad a=matklad I'll write a more comprehensive description when this is closer to being done. Basically this investigates one question: "how do we represent code which is a result of a macro call". This is an interesting question: currently everything is `FileId` based, but macro expansion does not have a file! Co-authored-by: Aleksey Kladov <[email protected]>
| * small renameAleksey Kladov2019-01-022-3/+3
| |
| * commentsAleksey Kladov2019-01-023-12/+35
| |
| * renameAleksey Kladov2019-01-022-2/+2
| |
| * move macro id to idsAleksey Kladov2019-01-015-40/+40
| |
| * move more stuff to idsAleksey Kladov2019-01-016-185/+183
| |
| * rename MFileId -> HirFileIdAleksey Kladov2019-01-0113-99/+135
| |
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-27 19:55:24 +0000