aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
| * | wipFlorian Diebold2020-03-165-94/+160
| | |
| * | Attempt to implement ranking of rules when none matches perfectly (wip)Florian Diebold2020-03-163-11/+51
| | |
| * | Make MBE expansion more resilient (WIP)Florian Diebold2020-03-1610-91/+168
| |/
* | Merge #3624bors[bot]2020-03-173-131/+145
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 3624: Tidier tidy checks r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * | Tidier tidy checksAleksey Kladov2020-03-173-131/+145
|/ /
* | Merge pull request #3618 from swarnimarun/patch-1Aleksey Kladov2020-03-171-0/+1
|\ \ | | | | | | Gate release action to rust-analyzer owner
| * | Update .github/workflows/release.yamlAleksey Kladov2020-03-171-1/+1
| | | | | | | | | Co-Authored-By: Florian Diebold <[email protected]>
| * | Gate release action to rust-analyzer ownerSwarnim Arun2020-03-161-0/+1
| | |
* | | Merge #3616bors[bot]2020-03-171-16/+7
|\ \ \ | |/ / |/| | | | | | | | | | | | | | | | | 3616: Update dependencies, removing rustc_version r=matklad a=kjeremy Co-authored-by: kjeremy <[email protected]>
| * | Update dependencies, removing rustc_versionkjeremy2020-03-161-16/+7
| |/
* | Merge #3614bors[bot]2020-03-167-65/+80
|\ \ | |/ |/| | | | | | | | | | | | | | | | | 3614: Separate persistent mutable state from config r=matklad a=matklad That way, we clearly see which things are not change, and we also clearly see which things are persistent. r? @Veetaha Co-authored-by: Aleksey Kladov <[email protected]>
| * Separate persistent mutable state from configAleksey Kladov2020-03-167-65/+80
| | | | | | | | | | That way, we clearly see which things are not change, and we also clearly see which things are persistent.
| * Fix audit caching betterAleksey Kladov2020-03-161-1/+2
| |
* | Merge pull request #3612 from matklad/audit5Aleksey Kladov2020-03-161-1/+2
|\ \ | |/ |/| Fix audit caching better
| * Fix audit caching betterAleksey Kladov2020-03-161-1/+2
| |
* | Merge pull request #3611 from matklad/audit4Aleksey Kladov2020-03-161-1/+2
|\| | | | | Fix cargo audit caching
| * Fix cargo audit cachingAleksey Kladov2020-03-161-1/+2
|/ | | | | | See https://github.com/actions/cache/issues/133#issuecomment-599102035 for chown bit
* Merge pull request #3610 from matklad/audit3Aleksey Kladov2020-03-161-1/+14
|\ | | | | Cache cargo-audit on CI
| * Actually make npm audit more robustAleksey Kladov2020-03-161-1/+1
| | | | | | | | In bash, && and || have the same priority.
| * Cache cargo-audit on CIAleksey Kladov2020-03-161-0/+13
| | | | | | | | closes #3399
* | Merge #3584bors[bot]2020-03-1651-794/+813
|\ \ | |/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | 3584: Switch to dynamic dispatch r=matklad a=matklad Benches are in https://github.com/rust-analyzer/rust-analyzer/issues/1987#issuecomment-598807185 TL;DR: * 33% faster release build * slightly worse/same perf * no changes for debug build * slightly smaller binary cc @flodiebold I genuinely don't know if it is a good idea or not. Co-authored-by: Aleksey Kladov <[email protected]>
| * Use `dyn Trait` for working with databseAleksey Kladov2020-03-1651-794/+813
|/ | | | | | | It improves compile time in `--release` mode quite a bit, it doesn't really slow things down and, conceptually, it seems closer to what we want the physical architecture to look like (we don't want to monomorphise EVERYTHING in a single leaf crate).
* Merge pull request #3607 from murlakatamenka/masterAleksey Kladov2020-03-161-0/+15
|\ | | | | Add installation notes for Arch Linux users
| * User Manual: fix AUR linkmurlakatamenka2020-03-161-1/+1
| |
| * Add installation notes for Arch Linux usersmurlakatamenka2020-03-161-0/+15
| |
* | Merge pull request #3608 from matklad/audit2Aleksey Kladov2020-03-161-0/+4
|\ \ | |/ |/| Retry rust audit as well
| * Retry rust audit as wellAleksey Kladov2020-03-161-0/+4
|/ | | | https://github.com/rust-analyzer/rust-analyzer/runs/511553989?check_suite_focus=true#step:3:6
* Merge #3604bors[bot]2020-03-161-1/+1
|\ | | | | | | | | | | | | | | 3604: Remove dat fixme r=matklad a=Veetaha Cleanup as per #3603 Co-authored-by: Veetaha <[email protected]>
| * Remove dat fixmeVeetaha2020-03-161-1/+1
| |
* | Merge pull request #3606 from matklad/auditAleksey Kladov2020-03-163-23/+23
|\ \ | | | | | | Make audit more reliable
| * | Make audit more reliableAleksey Kladov2020-03-161-1/+1
| | | | | | | | | | | | | | | | | | I've seen this transient error a couple of times: https://github.com/rust-analyzer/rust-analyzer/runs/511162809?check_suite_focus=true#step:5:8
| * | :arrow_up: npmAleksey Kladov2020-03-162-22/+22
|/ /
* / Fix versionAleksey Kladov2020-03-161-1/+1
|/
* Merge #3573bors[bot]2020-03-161-0/+1
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 3573: Check all crates of the workspace r=matklad a=matklad Previously, if the root of the was was a real crate, only this crate was checked. Ideally, we might want some kind of config here (which might be just overriding the whole command), but `--workspace` is def a nicer default. r? @kiljacken Co-authored-by: Aleksey Kladov <[email protected]>
| * Check all crates of the workspaceAleksey Kladov2020-03-131-0/+1
| | | | | | | | | | | | | | | | | | Previously, if the root of the was was a real crate, only this crate was checked. Ideally, we might want some kind of config here (which might be just overriding the whole command), but `--workspace` is def a nicer default.
* | Merge #3587bors[bot]2020-03-162-11/+77
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 3587: Use WorkDoneProgress LSP API for initial load r=matklad a=slyngbaek Addresses #3283 Rather than using custom UI for showing the loaded state. Rely on the WorkDoneProgress API in 3.15.0 https://microsoft.github.io/language-server-protocol/specification#workDoneProgress. No client-side work was necessary. The UI is not exactly what is described in the issue but afaict that's how VS Code implements the LSP API. - The WorkDoneProgressEnd does not appear to display its message contents (controlled by vscode) Co-authored-by: Steffen Lyngbaek <[email protected]>
| * | Fix tests part 2...Steffen Lyngbaek2020-03-161-34/+31
| | |
| * | Fix broken testsSteffen Lyngbaek2020-03-161-26/+29
| | | | | | | | | | | | - Handle case of no projects. The notification still needs to be posted
| * | Rely on the safer workspace_loaded checkSteffen Lyngbaek2020-03-161-13/+15
| | |
| * | Fix broken testsSteffen Lyngbaek2020-03-141-5/+10
| | | | | | | | | | | | - Properly wait for workspace loading to be done
| * | Use idiomatic way of defining floatsSteffen Lyngbaek2020-03-131-2/+2
| | |
| * | Use WorkDoneProgress LSP API for initial loadSteffen Lyngbaek2020-03-131-6/+65
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Addresses #3283 Rather than using custom UI for showing the loaded state. Rely on the WorkDoneProgress API in 3.15.0 https://microsoft.github.io/language-server-protocol/specification#workDoneProgress. No client-side work was necessary. The UI is not exactly what is described in the issue but afaict that's how VS Code implements the LSP API. - The WorkDoneProgressEnd does not appear to display its message contents (controlled by vscode)
* | | Merge #3603bors[bot]2020-03-166-10/+28
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 3603: Fix crate display name dashes r=matklad a=SomeoneToIgnore A follow-up of https://github.com/rust-analyzer/rust-analyzer/pull/3602#discussion_r392733525 Co-authored-by: Kirill Bulatov <[email protected]>
| * | | Use Display instead of a custom methodKirill Bulatov2020-03-163-19/+17
| | | |
| * | | Fix crate display name dashesKirill Bulatov2020-03-166-20/+40
| | | |
* | | | Merge #3534bors[bot]2020-03-1613-147/+454
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 3534: Feature: vscode impl nightlies download and installation r=Veetaha a=Veetaha I need to test things more, but the core shape of the code is quite well-formed. The main problem is that we save the release date only for nightlies and there are no means to get the release date of the stable extension (i.e. for this we would need to consult the github releases via a network request, or we would need to somehow save this info into package.json or any other file accessible from the extension code during the deployment step, but this will be very hard I guess). So there is an invariant that the users can install nightly only from our extension and they can't do it manually, because when installing the nightly `.vsix` we actually save its release date to `globalState` Closes: #3402 TODO: - [x] More manual tests and documentation cc @matklad @lnicola Co-authored-by: Veetaha <[email protected]> Co-authored-by: Veetaha <[email protected]>
| * | | | vscode-postrefactor: migrate to arrow functionsVeetaha2020-03-161-2/+2
| | | | |
| * | | | vscode-postrefactor: fix syntax errorVeetaha2020-03-161-1/+1
| | | | |
| * | | | vscode-postrefactor: prefer arrow functionsVeetaha2020-03-161-1/+1
| | | | |
| * | | | vscode: sync package-lock.json version with package.jsonVeetaha2020-03-141-1/+1
| | | | |
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-05 06:54:46 +0000