Changelog #151

Author: lnicola

generated_assists.adoc

@@ -477,6 +477,52 @@ fn main() {
 ```
 
 
+[discrete]
+=== `convert_named_struct_to_tuple_struct`
+**Source:** https://github.com/rust-lang/rust-analyzer/blob/master/crates/ide-assists/src/handlers/convert_named_struct_to_tuple_struct.rs#L11[convert_named_struct_to_tuple_struct.rs]
+
+Converts struct with named fields to tuple struct, and analogously for enum variants with named
+fields.
+
+.Before
+```rust
+struct Point┃ { x: f32, y: f32 }
+
+impl Point {
+    pub fn new(x: f32, y: f32) -> Self {
+        Point { x, y }
+    }
+
+    pub fn x(&self) -> f32 {
+        self.x
+    }
+
+    pub fn y(&self) -> f32 {
+        self.y
+    }
+}
+```
+
+.After
+```rust
+struct Point(f32, f32);
+
+impl Point {
+    pub fn new(x: f32, y: f32) -> Self {
+        Point(x, y)
+    }
+
+    pub fn x(&self) -> f32 {
+        self.0
+    }
+
+    pub fn y(&self) -> f32 {
+        self.1
+    }
+}
+```
+
+
 [discrete]
 === `convert_to_guarded_return`
 **Source:** https://github.com/rust-lang/rust-analyzer/blob/master/crates/ide-assists/src/handlers/convert_to_guarded_return.rs#L21[convert_to_guarded_return.rs]

generated_diagnostic.adoc

@@ -18,6 +18,12 @@ This diagnostic is shown for code with inactive `#[cfg]` attributes.
 This diagnostic is triggered if an item name doesn't follow https://doc.rust-lang.org/1.0.0/style/style/naming/README.html[Rust naming convention].
 
 
+=== incorrect-try-target
+**Source:** https://github.com/rust-lang/rust-analyzer/blob/master/crates/ide-diagnostics/src/handlers/incorrect_try_expr.rs#L5[incorrect_try_expr.rs]
+
+This diagnostic is triggered if a question mark operator was used in a context where it is not applicable.
+
+
 === invalid-derive-target
 **Source:** https://github.com/rust-lang/rust-analyzer/blob/master/crates/ide-diagnostics/src/handlers/invalid_derive_target.rs#L3[invalid_derive_target.rs]
 
@@ -75,6 +81,12 @@ This diagnostic is triggered if an operation marked as `unsafe` is used outside
 This diagnostic is triggered if created structure does not have field provided in record.
 
 
+=== not-implemented
+**Source:** https://github.com/rust-lang/rust-analyzer/blob/master/crates/ide-diagnostics/src/handlers/not_implemented.rs#L5[not_implemented.rs]
+
+This diagnostic is triggered if a type doesn't implement a necessary trait.
+
+
 === replace-filter-map-next-with-find-map
 **Source:** https://github.com/rust-lang/rust-analyzer/blob/master/crates/ide-diagnostics/src/handlers/replace_filter_map_next_with_find_map.rs#L11[replace_filter_map_next_with_find_map.rs]
 

manual.adoc

@@ -174,14 +174,25 @@ On Unix, running the editor from a shell or changing the `.desktop` file to set
 
 ==== `rustup`
 
-`rust-analyzer` is available in `rustup`, but only in the nightly toolchain:
+`rust-analyzer` is available in `rustup`:
 
 [source,bash]
 ----
-$ rustup +nightly component add rust-analyzer-preview
+$ rustup component add rust-analyzer
 ----
 
-However, in contrast to `component add clippy` or `component add rustfmt`, this does not actually place a `rust-analyzer` binary in `~/.cargo/bin`, see https://github.com/rust-lang/rustup/issues/2411[this issue].
+However, in contrast to `component add clippy` or `component add rustfmt`, this does not actually place a `rust-analyzer` binary in `~/.cargo/bin`, see https://github.com/rust-lang/rustup/issues/2411[this issue]. You can find the path to the binary using:
+[source,bash]
+----
+$ rustup which --toolchain stable rust-analyzer
+----
+You can link to there from `~/.cargo/bin` or configure your editor to use the full path.
+
+Alternatively you might be able to configure your editor to start `rust-analyzer` using the command:
+[source,bash]
+----
+$ rustup run stable rust-analyzer
+----
 
 ==== Arch Linux
 

thisweek/_posts/2022-10-17-changelog-151.adoc

@@ -0,0 +1,41 @@
+= Changelog #151
+:sectanchors:
+:page-layout: post
+
+Commit: commit:0531aab522f25d6aae30b2cc23a09f4b9257eedc[] +
+Release: release:2022-10-17[]
+
+== New Features
+
+* pr:13358[] (first contribution) complete Cargo environment variables in `env!` and `option_env!`:
++
+video::https://user-images.githubusercontent.com/308347/196144995-64e38e3c-0ad7-4cf3-b0f7-4243866ed341.mp4[options=loop]
+* pr:13303[] add `Convert named to tuple struct` assist:
++
+video::https://user-images.githubusercontent.com/308347/196149918-7a27df57-b525-40cf-ae12-bc58e077d637.mp4[options=loop]
+* pr:13354[] diagnose some incorrect usages of the question mark operator:
++
+video::https://user-images.githubusercontent.com/308347/196147506-111000e4-60a9-4dd2-8f0b-252d766b3cb5.mp4[options=loop]
+
+== Fixes
+
+* pr:13420[] (first contribution) don't trigger auto-import assist on parameter names.
+* pr:13391[] (first contribution) update installation instructions for the stable `rustup` component.
+* pr:13380[] honor `cfg` attributes on params when lowering patterns.
+* pr:13384[] expand unmatched macro-by-example fragments to reasonable default token trees.
+* pr:13382[] reorder `dyn` bounds on render.
+* pr:13392[] prefer similar tokens when expanding macros speculatively.
+* pr:13333[] fix placement of and indentation inside generated methods.
+* pr:13377[] underline only intra-doc links instead of the whole doc comment.
+* pr:13402[] cast `runnableEnv` items to string.
+
+== Internal Improvements
+
+* pr:13397[] (first contribution) fix links in `syntax.md`.
+* pr:13376[] add `GenericParamList::to_generic_args` and `{TypeParam,ConstParam}::remove_default` APIs.
+* pr:13385[] don't report build scripts and proc macros as metadata progress.
+* pr:13386[] refactor completion expansion.
+* pr:13357[] allow `minicore` flags specifications to be order independent.
+* pr:13401[] run `analysis-stats` on CI, with `opt-level = 1`.
+* pr:13415[] set a timeout when publishing to OVSX.
+* pr:13408[] bump `chalk`.