aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Fix quotesAleksey Kladov2020-03-091-1/+1
| | | | closes #3501
* Merge #3528bors[bot]2020-03-091-1/+2
|\ | | | | | | | | | | | | | | | | | | | | 3528: Print crate name in profil r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * Print crate name in profilAleksey Kladov2020-03-091-1/+2
|/
* Merge #3527bors[bot]2020-03-099-56/+37
|\ | | | | | | | | | | | | | | | | | | | | 3527: Simplify r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * SimplifyAleksey Kladov2020-03-092-8/+2
| |
| * SimplifyAleksey Kladov2020-03-091-18/+8
| |
| * Minimize APIAleksey Kladov2020-03-092-7/+3
| |
| * Use `Index` for CrateGraphAleksey Kladov2020-03-099-23/+24
| |
* | Merge #3526bors[bot]2020-03-092-3/+12
|\ \ | |/ |/| | | | | | | | | | | | | 3526: Silence "file out of workspace" errors r=matklad a=matklad We really should fix this limitation of the VFS, but it's some way off at the moment, so let's just silence the user-visible error for now. Co-authored-by: Aleksey Kladov <[email protected]>
| * Silence "file out of workspace" errorsAleksey Kladov2020-03-092-3/+12
| | | | | | | | | | We really should fix this limitation of the VFS, but it's some way off at the moment, so let's just silence the user-visible error for now.
* | Merge #3519bors[bot]2020-03-0918-121/+270
|\ \ | |/ |/| | | | | | | | | | | 3519: Show mod path on hover r=matklad a=SomeoneToIgnore Closes #1064 Co-authored-by: Kirill Bulatov <[email protected]>
| * Less abstract CrateData apiKirill Bulatov2020-03-099-51/+48
| |
| * Consider crate declaration namesKirill Bulatov2020-03-0811-86/+135
| |
| * Show mod path in hover tooltipKirill Bulatov2020-03-074-29/+132
| |
* | Merge pull request #3525 from matklad/ciAleksey Kladov2020-03-091-0/+1
|\ \ | | | | | | Install Node only for Linux
| * | Install Node only for LinuxAleksey Kladov2020-03-091-0/+1
| | | | | | | | | | | | | | | | | | Hopefully, this will lead to fewer errors like https://github.com/rust-analyzer/rust-analyzer/runs/493983317?check_suite_focus=true#step:5:10
* | | Merge #3514bors[bot]2020-03-095-24/+54
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 3514: vscode: askBeforeDownload option r=matklad a=Veetaha This is a small step towards #3402, also implements my proposal stated in #3403 Also renamed `BinarySource` to `ArtifactSource` in anticipation of nightlies installation that requires downloading not a binary itself but `.vsix` package, thus generalized to `artifact` term. @matklad @lnicola Co-authored-by: Veetaha <[email protected]>
| * | | vscode: groupd updates-related config under `updates` section as per @matkladVeetaha2020-03-093-3/+3
| | | |
| * | | vscode: fix inversion of askBeforeDownloadVeetaha2020-03-081-1/+1
| | | |
| * | | docs: change formattingVeetaha2020-03-081-6/+16
| | | |
| * | | vscode: rename alwaysDownloadServer -> askBeforeDownloadVeetaha2020-03-083-5/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The new name seems much simpler and it doesn't limit this config value only to downloading the server binary. Thus we wouldn't need to create another config properties to handle other downloads whatsoever. Anyway, I believe (heuristically) that most of the users would want to set "askBeforeDownload": false once and never bother clicking on the notification again (because otherwise there is no big point in installing rust-analyzer if it cannot install the server)
| * | | vscode: add docs on alwaysDownloadServerVeetaha2020-03-081-1/+8
| | | |
| * | | vscode: care about alwaysDownloadServer option before askingVeetaha2020-03-073-23/+31
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Also renamed BinarySource to ArtifactSource in anticipation of nightlies installation that requires downloading not a binary itself but .vsix package, thus generalized to `artifact` term
| * | | vscode: contribute "alwaysDownloadServer" option to configVeetaha2020-03-071-0/+5
| | |/ | |/|
* | | Merge #3513bors[bot]2020-03-0914-42/+528
|\ \ \ | |_|/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | 3513: Completion in macros r=matklad a=flodiebold I experimented a bit with completion in macros. It's kind of working, but there are a lot of rough edges. - I'm trying to expand the macro call with the inserted fake token. This requires some hacky additions on the HIR level to be able to do "hypothetical" expansions. There should probably be a nicer API for this, if we want to do it this way. I'm not sure whether it's worth it, because we still can't do a lot if the original macro call didn't expand in nearly the same way. E.g. if we have something like `println!("", x<|>)` the expansions will look the same and everything is fine; but in that case we could maybe have achieved the same result in a simpler way. If we have something like `m!(<|>)` where `m!()` doesn't even expand or expands to something very different, we don't really know what to do anyway. - Relatedly, there are a lot of cases where this doesn't work because either the original call or the hypothetical call doesn't expand. E.g. if we have `m!(x.<|>)` the original token tree doesn't parse as an expression; if we have `m!(match x { <|> })` the hypothetical token tree doesn't parse. It would be nice if we could have better error recovery in these cases. Co-authored-by: Florian Diebold <[email protected]>
| * | Move hypothetical expansion to hir_expandFlorian Diebold2020-03-084-39/+43
| | |
| * | Remove TODOsFlorian Diebold2020-03-071-5/+6
| | |
| * | Fix CompletionContext module field (by removing it)Florian Diebold2020-03-073-8/+6
| | | | | | | | | | | | | | | Two uses only needed the crate; one was wrong and should use the module from the scope instead.
| * | Add some sanity checksFlorian Diebold2020-03-071-1/+10
| | |
| * | Fix record pattern completionFlorian Diebold2020-03-073-1/+30
| | |
| * | Fix record literal completionFlorian Diebold2020-03-072-3/+33
| | |
| * | Fix range for postfix snippetsFlorian Diebold2020-03-071-2/+63
| | |
| * | Add more testsFlorian Diebold2020-03-073-1/+54
| | |
| * | Try to complete within macrosFlorian Diebold2020-03-079-38/+339
| |/
* | Merge #3516bors[bot]2020-03-094-19/+217
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | 3516: Handle visibility in more cases in completion r=matklad a=flodiebold This means we don't show private items when completing paths or method calls. We might want to show private items if we can edit their definition and provide a "make public" assist, but I feel like we'd need better sorting of completion items for that, so they can be not shown or sorted to the bottom by default. Until then, they're usually more of a distraction to me. Co-authored-by: Florian Diebold <[email protected]>
| * | Handle visibility for assoc item path completion as wellFlorian Diebold2020-03-083-22/+124
| | |
| * | Handle visibility for path completion (not in all cases yet)Florian Diebold2020-03-082-5/+51
| | |
| * | Handle visibility in method call completionFlorian Diebold2020-03-073-4/+54
| |/
* | Merge #3518bors[bot]2020-03-095-37/+213
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 3518: Add parse_to_token_tree r=matklad a=edwin0cheng This PR introduce a function for parsing `&str` to `tt::TokenTree`: ```rust // Convert a string to a `TokenTree` pub fn parse_to_token_tree(text: &str) -> Option<(tt::Subtree, TokenMap)> { ```` Co-authored-by: Edwin Cheng <[email protected]>
| * | Add parse_to_token_treeEdwin Cheng2020-03-085-37/+213
| | |
* | | Merge #3524bors[bot]2020-03-091-0/+3
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 3524: Ignore client-specific notifications r=matklad a=matklad closes #3523 bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * | | Ignore client-specific notificationsAleksey Kladov2020-03-091-0/+3
| | | | | | | | | | | | | | | | closes #3523
* | | | Merge #3520bors[bot]2020-03-091-0/+32
|\ \ \ \ | |/ / / |/| | | | | | | | | | | | | | | | | | | | | | | 3520: Omit unit struct hints r=matklad a=SomeoneToIgnore Closes https://github.com/rust-analyzer/rust-analyzer/issues/3488 Co-authored-by: Kirill Bulatov <[email protected]>
| * | | Omit unit struct hintsKirill Bulatov2020-03-081-0/+32
| | |/ | |/|
* | | Merge #3521bors[bot]2020-03-081-9/+9
|\ \ \ | |/ / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 3521: Use markdown description in vscode r=matklad a=vbfox By using `markdownDescription` the markdown in the description is parsed and displayed. Before: ![image](https://user-images.githubusercontent.com/131878/76171725-cb2a0380-618e-11ea-956f-7668a746946f.png) After: ![image](https://user-images.githubusercontent.com/131878/76171743-00365600-618f-11ea-8847-f4ab09639bb5.png) Co-authored-by: Julien Roncaglia <[email protected]>
| * | Use markdown description in vscodeJulien Roncaglia2020-03-081-9/+9
|/ /
* | Merge #3378bors[bot]2020-03-074-134/+202
|\ \ | |/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 3378: vscode: redesign inlay hints to be capable of handling multiple editors for one source file r=Veetaha a=Veetaha Fixes: #3008 (inlay corruption with multiple editors for one file). Fixes: #3319 (unnecessary requests for inlay hints when switching unrelated source files or output/log/console windows) Also, I don't know how, but the problem described in #3057 doesn't appear for me anymore (maybe it was some fix on the server-side, idk), the inlay hints are displaying right away. Though the last time I checked this it was caused by the server returning an empty array of hints and responding with a very big latency, I am not sure that this redesign actually fixed #3057.... We didn't handle the case when one rust source file is open in multiple editors in vscode (e.g. by manually adding another editor for the same file or by opening an inline git diff view or just any kind of preview within the same file). The git diff preview is actually quite special because it causes memory leaks in vscode (https://github.com/microsoft/vscode/issues/91782). It is not removed from `visibleEditors` once it is closed. However, this bug doesn't affect the inlay hints anymore, because we don't issue a request and set inlay hints for each editor in isolation. Editors are grouped by their respective files and we issue requests only for files and then update all duplicate editors using the results (so we just update the decorations for already closed git diff preview read-only editors). Also, note on a hack I had to use. `vscode.TextEdtior` identity is not actually public, its `id` field is not exposed to us. I created a dedicated upstream issue for this (https://github.com/microsoft/vscode/issues/91788). Regarding #3319: the newly designed hints client doesn't issue requests for type hints when switching the visible editors if it has them already cached (though it does rerender things anyway, but this could be optimized in future if so wanted). <details> <summary>Before</summary> ![bug_demo](https://user-images.githubusercontent.com/36276403/75613171-3cd0d480-5b33-11ea-9066-954fb2fb18a5.gif) </details> <details> <summary> After </summary> ![multi-cursor-replace](https://user-images.githubusercontent.com/36276403/75612710-d5b12100-5b2e-11ea-99ba-214b4219e6d3.gif) </details> Co-authored-by: Veetaha <[email protected]>
| * vscode: post refactor HintsUpdater (simplify create() -> constructor call)Veetaha2020-03-071-16/+10
| |
| * vscode: more privacy for HintsUpdaterVeetaha2020-03-071-1/+1
| |
| * vscode: remove logging from inlays, run fix lint issuesVeetaha2020-03-071-18/+7
| |
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-30 03:37:01 +0000