|
| 1 | += Changelog #154 |
| 2 | +:sectanchors: |
| 3 | +:page-layout: post |
| 4 | + |
| 5 | +Commit: commit:d03c1c87d4ca2d524646316387d47b12524ac451[] + |
| 6 | +Release: release:2022-11-07[] |
| 7 | + |
| 8 | +== An Update on OpenVSX == |
| 9 | + |
| 10 | +Many users of VS Code are actually running an open-source version of the editor. |
| 11 | +These include VSCodium and the `code` package in Arch Linux. |
| 12 | +The "free" builds are not allowed to connect to the Microsoft Marketplace and instead they download extensions from https://open-vsx.org[OpenVSX]. |
| 13 | + |
| 14 | +For a long time, the version of rust-analyzer available on OpenVSX was outdated and did not work very well with recent Rust toolchains. |
| 15 | +But because of various technical reasons, we were not able to publish new versions there. |
| 16 | +This caused countless of disappointed users, and dozens of duplicate issues filed against our tracker. |
| 17 | + |
| 18 | +Last week, with the help of the OpenVSX maintainers, we managed to sort out the issues. |
| 19 | +And for the first time in almost a year, rust-analyzer is https://open-vsx.org/extension/rust-lang/rust-analyzer[available] on OpenVSX. |
| 20 | +Unfortunately, we had to remove the existing versions, under the identifier of `matklad.rust-analyzer`. |
| 21 | +If you have that version installed, it will not be automatically switched over to the new one (`rust-lang.rust-analyzer`). |
| 22 | + |
| 23 | +So if you are not running a Microsoft build of VS Code, our advice is to reinstall rust-analyzer from Code's extension page. |
| 24 | +This will ensure that you get updated versions in the future. |
| 25 | +If you've installed a VSIX from GitHub since March, it should get updated automatically, but it doesn't hurt to check. |
| 26 | + |
| 27 | +If you are using an official build of Code, or a different editor, you don't need to take any action. |
| 28 | + |
| 29 | +== New Features |
| 30 | + |
| 31 | +* pr:13525[] show signature help when calling generic types implementing `FnOnce`: |
| 32 | ++ |
| 33 | +image::https://user-images.githubusercontent.com/308347/200243832-b81303bd-b833-4d99-b96c-ecec6acdc2df.png["A screenshot showing signature help when calling a `FnOnce` parameter"] |
| 34 | +* pr:13516[] add "Convert `match` to `let`-``else``" assist: |
| 35 | ++ |
| 36 | +video::https://user-images.githubusercontent.com/308347/200244795-545f0465-ec0f-4d8c-8f70-5f08aea99bf0.mp4[options=loop] |
| 37 | +* pr:13527[] use `let`-`else` statements in "Convert to guarded return". |
| 38 | +* pr:13359[] add `rust-analyzer.assist.emitMustUse` config for inserting `#[must_use]` in `generate_enum_as_method`. |
| 39 | + |
| 40 | +== Fixes |
| 41 | + |
| 42 | +* pr:13454[] (first contribution) handle shadowing of locals in "Inline call". |
| 43 | +* pr:13508[] (first contribution) don't offer to remove unnecessary `async` in trait items. |
| 44 | +* pr:13523[] disregard type variable expectation for `if` expressions. |
| 45 | +* pr:13546[] lower unsafety of function pointer and item types. |
| 46 | +* pr:13517[] make custom expression prefix completions understand references. |
| 47 | +* pr:13549[] fix reference searching accounting for substrings instead of whole identifiers. |
| 48 | +* pr:13456[] generate SCIP symbols for local crates. |
| 49 | + |
| 50 | +== Internal Improvements |
| 51 | + |
| 52 | +* pr:13445[] (first contribution) fix some broken links in `guide.md`. |
| 53 | +* pr:13536[], pr:13556[] (first contribution) mention auto-published crates in the manual. |
| 54 | +* pr:13379[], pr:13435[] migrate assists to format args captures, parts 1 and 3. |
| 55 | +* pr:13544[] add rustbot features related to PR state labels. |
| 56 | +* pr:13541[] clarify which VS Code commands are meant for debugging. |
0 commit comments