You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
*[`assertions_on_result_states` avoid changing return type in more cases](https://github.com/rust-lang/rust-clippy/pull/15591)
155
+
*[`collapsible_match` suggest ref/derefs when needed](https://github.com/rust-lang/rust-clippy/pull/14221)
156
+
*[enable `clippy::panic` in const contexts](https://github.com/rust-lang/rust-clippy/pull/15565)
157
+
*[fix false positive of `needless_range_loop` when meeting multidimensional array](https://github.com/rust-lang/rust-clippy/pull/15486)
158
+
*[fix `alloc_instead_of_core` false positive when `alloc` is an alias](https://github.com/rust-lang/rust-clippy/pull/15581)
159
+
*[fix `needless_for_each` suggesting wrongly with explicit closure input types](https://github.com/rust-lang/rust-clippy/pull/15595)
160
+
*[fix `print_literal` suggesting wrongly for inline literal following a numbered arg](https://github.com/rust-lang/rust-clippy/pull/15583)
161
+
*[fix `redundant_closure` suggests wrongly with deref overload](https://github.com/rust-lang/rust-clippy/pull/15077)
162
+
*[supress `excessive_precision` when constants are overly precise](https://github.com/rust-lang/rust-clippy/pull/15193)
163
+
164
+
#### Rust-Analyzer
165
+
*[add progress bars to more places in analysis-stats](https://github.com/rust-lang/rust-analyzer/pull/20560)
166
+
*[attach the db in one more place in highlighting](https://github.com/rust-lang/rust-analyzer/pull/20553)
167
+
*[avoid `--target` option being given twice to `rustc` when invoked through `cargo rustc` while fetching target data layout](https://github.com/rust-lang/rust-analyzer/pull/20579)
168
+
*[deduplicate methods in completion by function ID and not by name](https://github.com/rust-lang/rust-analyzer/pull/20587)
169
+
*[in `highlight_related,` when on an unsafe block, don't highlight unsafe operations of other unsafe blocks](https://github.com/rust-lang/rust-analyzer/pull/20547)
170
+
*[when mapping next-solver's `dyn` type, add `Self` (aka. bound var ^1.0) to auto traits' substitutions](https://github.com/rust-lang/rust-analyzer/pull/20563)
171
+
*[cache trait solving across queries in the same revision](https://github.com/rust-lang/rust-analyzer/pull/20527)
127
172
128
173
### Rust Compiler Performance Triage
129
174
@@ -325,7 +370,13 @@ Please see the latest [Who's Hiring thread on r/rust](INSERT_LINK_HERE)
325
370
326
371
# Quote of the Week
327
372
328
-
<!-- QOTW goes here -->
373
+
> Bugs like this are the worst! It's almost impossible to catch them in development, because there is never enough load on the system to force the scheduler to move the execution to another thread. So, you end up with one of these "impossible to reproduce, fails sometimes, but never for you" bugs.
374
+
>
375
+
> It's mind-blowingly cool that the Rust compiler can detect something like this. And that seemingly unrelated parts of the language, like mutexes, lifetimes and async operations form such a coherent system.
376
+
377
+
– [Bernard Kolobara on their blog](https://lubeno.dev/blog/rusts-productivity-curve)
378
+
379
+
Thanks to [llogiq](https://users.rust-lang.org/t/twir-quote-of-the-week/328/1711) for the suggestion!
329
380
330
381
[Please submit quotes and vote for next week!](https://users.rust-lang.org/t/twir-quote-of-the-week/328)
0 commit comments