aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
| * cargo updatekjeremy2020-09-021-4/+4
|/
* Merge #5931bors[bot]2020-09-012-158/+184
|\ | | | | | | | | | | | | | | 5931: Update vscode to 1.47 and update the rest of our npm packages r=kjeremy a=kjeremy Co-authored-by: kjeremy <[email protected]>
| * Update the rest of our node packageskjeremy2020-09-012-137/+163
| |
| * Bump minimum vscode to 1.47kjeremy2020-09-012-21/+21
| |
* | Merge #5927bors[bot]2020-09-011-0/+8
|\ \ | |/ |/| | | | | | | | | | | 5927: Document VS Code setting needed for on-typing assists r=matklad a=arzg Fixes #5925. Co-authored-by: Aramis Razzaghipour <[email protected]>
| * Document VS Code setting needed for on-typing assistsAramis Razzaghipour2020-09-011-0/+8
| |
* | Merge #5929bors[bot]2020-09-012-69/+211
|\ \ | |/ |/| | | | | | | | | | | 5929: Upgrade mocha from `npm audit fix` r=matklad a=kjeremy Co-authored-by: kjeremy <[email protected]>
| * Upgrade mocha from `npm audit fix`kjeremy2020-09-012-69/+211
|/
* Merge #5926bors[bot]2020-09-011-1/+1
|\ | | | | | | | | | | | | | | | | | | 5926: Bump token expansion limit r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * Bump token expansion limitAleksey Kladov2020-09-011-1/+1
|/ | | | | | | We hit this for redis crate, reported at Reported at https://www.reddit.com/r/rust/comments/ikfsf8/rustanalyzer_doesnt_work_with_the_redis_crate/
* Merge #5923bors[bot]2020-09-012-10/+32
|\ | | | | | | | | | | | | | | | | 5923: "How I survived Git" tips r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * "How I survived Git" tipsAleksey Kladov2020-09-012-10/+32
|/
* Merge #5862bors[bot]2020-09-012-0/+17
|\ | | | | | | | | | | | | | | 5862: Add a test that forbids merge commits r=matklad a=dragfire Fixes #5854 Co-authored-by: dragfire <[email protected]>
| * Add a test that forbids merge commitsdragfire2020-08-312-0/+17
|/
* Merge #5921bors[bot]2020-08-311-2/+2
|\ | | | | | | | | | | | | | | 5921: Don't publish every day and do it only for release r=matklad a=pksunkara I think this is a good balance. Co-authored-by: Pavan Kumar Sunkara <[email protected]>
| * Don't publish every day and do it only for releasePavan Kumar Sunkara2020-08-311-2/+2
|/
* Merge #5920bors[bot]2020-08-312-27/+18
|\ | | | | | | | | | | | | | | | | | | 5920: Reduce path_from_text usage r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * Reduce path_from_text usageAleksey Kladov2020-08-312-13/+18
| |
| * Remove dead codeAleksey Kladov2020-08-311-14/+0
|/
* Merge #5914bors[bot]2020-08-304-45/+12
|\ | | | | | | | | | | | | | | 5914: Replace custom `xtask::not_bash::fs2` setup with fs_err crate r=matklad a=Veetaha Co-authored-by: Veetaha <[email protected]>
| * Replace custom `not_bash::fs2` setup with fs_err crateVeetaha2020-08-294-45/+12
| |
| |
| \
*-. \ Merge #5910 #5912bors[bot]2020-08-294-4/+3
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5910: Fix some typos r=matklad a=SomeoneToIgnore 5912: Remove fixme from inlay_hints.ts r=matklad a=Veetaha I have reevaluated the fixme and it doesn't seem necessary to pass an array of files to the inlay hints request. This will (a) make the request more compilcated (b), make us wait for inlay hints for `all` active editors resolve at once before rendering and (c) doesn't seem required because 99% of the time there is a single active editor in the IDE Co-authored-by: Kirill Bulatov <[email protected]> Co-authored-by: Veetaha <[email protected]>
| | * | Remove fixme from inlay_hints.tsVeetaha2020-08-291-1/+0
| | |/ | | | | | | | | | | | | | | | | | | | | | | | | I have reevaluated the fixme and it doesn't seem necessary to pass an array of files to the inlay hints request. This will (a) make the request more compilcated (b), make us wait for inlay hints for `all` active editors resolve at once before rendering and (c) doesn't seem required because 99% of the time there is a single active editor in the IDE
| * / Fix some typosKirill Bulatov2020-08-283-3/+3
| |/
* | Merge #5909bors[bot]2020-08-291-0/+8
|\ \ | |/ |/| | | | | | | | | | | 5909: Add rust-analyzer.checkOnSave.target to package.json r=matklad a=lnicola This was already implemented, but it's missing from the manifest. Co-authored-by: Laurențiu Nicola <[email protected]>
| * Add rust-analyzer.checkOnSave.target to package.jsonLaurențiu Nicola2020-08-281-0/+8
|/
* Merge #5908bors[bot]2020-08-281-0/+16
|\ | | | | | | | | | | | | | | | | | | 5908: fmt import r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * fmt importAleksey Kladov2020-08-281-0/+16
|/
* Merge #5907bors[bot]2020-08-2826-25/+25
|\ | | | | | | | | | | | | | | | | | | 5907: :arrow_up: expect-test r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * :arrow_up: expect-testAleksey Kladov2020-08-2826-25/+25
| |
* | Merge #5906bors[bot]2020-08-283-1/+215
|\ \ | |/ |/| | | | | | | | | | | 5906: Use SVG logo in readme r=matklad a=arzg This also adds the two versions of the logo created by @Aloso to `/assets` for any future uses. I found the logo SVGs in [this issue](https://github.com/rust-analyzer/rust-analyzer.github.io/issues/23). Co-authored-by: Aramis Razzaghipour <[email protected]>
| * Replace logo in readme with SVG versionAramis Razzaghipour2020-08-281-1/+3
| |
| * Add SVG logos to assets directoryAramis Razzaghipour2020-08-282-0/+212
|/
* Merge #5900bors[bot]2020-08-273-32/+29
|\ | | | | | | | | | | | | | | | | | | 5900: :arrow_up: crates r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * :arrow_up: cratesAleksey Kladov2020-08-273-32/+29
| |
* | Merge #5899bors[bot]2020-08-278-29/+38
|\| | | | | | | | | | | | | | | | | | | 5899: Add track_env_var to the proc macro server r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * CONST LOOPS ARE HEREAleksey Kladov2020-08-278-29/+38
|/
* Merge #5898bors[bot]2020-08-271-1/+2
|\ | | | | | | | | | | | | | | | | | | 5898: Minor r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * MinorAleksey Kladov2020-08-271-1/+2
|/
* Merge #5895bors[bot]2020-08-269-337/+297
|\ | | | | | | | | | | | | | | | | | | 5895: Tease apart orthogonal concerns in markdown link rewriting r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * Tease apart orthogonal concerns in markdown link rewritingAleksey Kladov2020-08-269-337/+297
| | | | | | | | | | | | | | | | | | | | | | | | `hir` should know nothing about URLs, markdown and html. It should only be able to: * resolve stringy path from documentation * generate canonical stringy path for a def In contrast, link rewriting should not care about semantics of paths and names resolution, and should be concern only with text mangling bits.
* | Merge #5893bors[bot]2020-08-262-2/+9
|\ \ | |/ |/| | | | | | | | | | | | | | | 5893: Allow running a test as a binary r=matklad a=jonas-schievink If a test uses `harness = false`, it just contains an `fn main` that is executed via `cargo test`. This adds support for that. Note though that Cargo doesn't actually tell us whether `harness = false`, so this hint will always show up when you put an `fn main` into an integration test. Normally people shouldn't be doing that if they do use the harness though. Co-authored-by: Jonas Schievink <[email protected]>
| * Allow running a test as a binaryJonas Schievink2020-08-262-2/+9
| |
* | Merge #5894bors[bot]2020-08-261-88/+74
|\ \ | |/ |/| | | | | | | | | | | | | | | 5894: Cleanup hover links tests r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * Cleanup hover links testsAleksey Kladov2020-08-261-88/+74
|/
* Merge #5887bors[bot]2020-08-262-19/+170
|\ | | | | | | | | | | | | | | 5887: Improve fenced code block support for doctests r=fmease a=fmease Fixes #5783 Co-authored-by: León Orell Valerian Liehr <[email protected]>
| * Improve support for code block attributesLeón Orell Valerian Liehr2020-08-262-19/+170
| |
* | Merge #5879bors[bot]2020-08-261-5/+3
|\ \ | |/ |/| | | | | | | | | | | | | 5879: Update mentions of 'ra_vfs' in architecture doc r=matklad a=rherrmann Adjust the paragraph about `ra_vfs` to point to the `vfs` crate that is used now. Co-authored-by: Rüdiger Herrmann <[email protected]>
| * Update mentions of 'ra_vfs' in architecture docRüdiger Herrmann2020-08-251-5/+3
| | | | | | Adjust the paragraph about `ra_vfs` to point to the `vfs` crate that is used now.
* | Merge #5885bors[bot]2020-08-263-49/+117
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5885: Make inlay hints colors more configurable r=matklad a=Veetaha **[BREAKING CHANGE]** Tackles https://github.com/rust-analyzer/rust-analyzer/issues/5337#issuecomment-680018601 and generally related to #5337. Added `foreground/background` color configurations with optional more specific overrides `foreground.(type|parameter|chaining)Hints`. One problem I see is that the config keys are long and don't fit into the on-hover hints in the `settings.json` file entirely... <details> <summary>Demo</summary> ![demo](https://user-images.githubusercontent.com/36276403/91238334-77fc3b00-e745-11ea-836b-2822015ece98.gif) </details> Co-authored-by: Veetaha <[email protected]>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-24 00:32:31 +0000