aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Check only one fixtureEdwin Cheng2020-03-101-1/+6
|
* Add fixture meta for single file fixtureEdwin Cheng2020-03-103-15/+56
|
* Merge #3546bors[bot]2020-03-103-14/+5
|\ | | | | | | | | | | | | | | | | | | | | 3546: :arrow_up: fst r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * :arrow_up: fstAleksey Kladov2020-03-103-14/+5
|/
* Merge #3545bors[bot]2020-03-101-12/+3
|\ | | | | | | | | | | | | | | 3545: Remove c2-chacha dependency r=kjeremy a=kjeremy Co-authored-by: kjeremy <[email protected]>
| * Remove c2-chaha dependencykjeremy2020-03-101-12/+3
|/
* Merge #3533bors[bot]2020-03-095-11/+10
|\ | | | | | | | | | | | | | | 3533: Updates insta to 0.15.0 and bumps console to 0.10.0 r=matklad a=kjeremy Co-authored-by: kjeremy <[email protected]>
| * Updates insta to 0.15.0 and bumps console to 0.10.0kjeremy2020-03-095-11/+10
| |
* | Merge #3532bors[bot]2020-03-094-7/+9
|\ \ | |/ |/| | | | | | | | | | | 3532: Fix SelectionRange return type r=matklad a=kjeremy Co-authored-by: kjeremy <[email protected]>
| * Fix SelectionRange return typekjeremy2020-03-094-7/+9
|/
* Set extension version during releaseAleksey Kladov2020-03-092-4/+10
|
* Disable jemalloc, it doesn't work out of the box with muslAleksey Kladov2020-03-091-1/+3
|
* Merge #3531bors[bot]2020-03-091-2/+6
|\ | | | | | | | | | | | | | | | | | | | | 3531: Use jemalloc for linux builds r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * Use jemalloc for linux buildsAleksey Kladov2020-03-091-2/+6
| |
* | Merge #3530bors[bot]2020-03-091-1/+1
|\| | | | | | | | | | | | | | | | | | | | | | | | | 3530: Fix quotes r=matklad a=matklad closes #3501 bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * 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]>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-09 18:23:58 +0000