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
*[`ItemTree`'s `ItemVisibilities` has no identity, so deduplicate](https://github.com/rust-lang/rust-analyzer/pull/19980)
165
+
*[add support for excluding imports from symbol search](https://github.com/rust-lang/rust-analyzer/pull/19996)
166
+
*[cleanup incremental tests and verify query executions](https://github.com/rust-lang/rust-analyzer/pull/20006)
167
+
*[add the quickfix for increasing visibility of a private field to the private-field diagnostic](https://github.com/rust-lang/rust-analyzer/pull/19945)
168
+
*[in "Fill match arms", allow users to prefer `Self` to the `enum` name when possible](https://github.com/rust-lang/rust-analyzer/pull/19939)
169
+
*[insert required parentheses when typing `+` in dyn trait type](https://github.com/rust-lang/rust-analyzer/pull/20015)
170
+
*[show what cargo metadata is doing in status](https://github.com/rust-lang/rust-analyzer/pull/20014)
171
+
*[copy lockfiles into target directory before invoking `cargo metadata`](https://github.com/rust-lang/rust-analyzer/pull/20018)
172
+
*[do not force descend into derives for goto IDE features](https://github.com/rust-lang/rust-analyzer/pull/19981)
173
+
*[fix comparison of proc macros](https://github.com/rust-lang/rust-analyzer/pull/19983)
174
+
*[fix completion with some attribute macros](https://github.com/rust-lang/rust-analyzer/pull/19942)
175
+
*[fix proc macro server handling of strings with minuses](https://github.com/rust-lang/rust-analyzer/pull/19970)
176
+
*[hide dyn inlay hints for incomplete `impl`s](https://github.com/rust-lang/rust-analyzer/pull/19973)
177
+
*[never make type mismatch diagnostic stable, even when there is a fix](https://github.com/rust-lang/rust-analyzer/pull/20022)
178
+
*[reload workspaces when cargo configs change](https://github.com/rust-lang/rust-analyzer/pull/20020)
179
+
*[support spans with proc macro servers from before the ast id changes](https://github.com/rust-lang/rust-analyzer/pull/19985)
180
+
*[generate annotations for macro defined items if their name is in the input](https://github.com/rust-lang/rust-analyzer/pull/19990)
181
+
*[idiomatic salsa use for `enum` variants query](https://github.com/rust-lang/rust-analyzer/pull/20007)
182
+
*[improve completions in if / while expression conditions](https://github.com/rust-lang/rust-analyzer/pull/20023)
183
+
*[optimize `pub(crate)` and `pub(self)` visibility resolution](https://github.com/rust-lang/rust-analyzer/pull/20009)
184
+
*[perf: bring back `EMPTY` item tree deduplication](https://github.com/rust-lang/rust-analyzer/pull/19991)
185
+
*[provide better incrementality when items are changed](https://github.com/rust-lang/rust-analyzer/pull/19837)
186
+
*[simplify and optimize `ItemTree`](https://github.com/rust-lang/rust-analyzer/pull/19982)
187
+
*[turn `BlockId` into a `#[salsa::tracked]`](https://github.com/rust-lang/rust-analyzer/pull/19995)
188
+
*[use `ThinVec` in `ItemScope` in a couple places](https://github.com/rust-lang/rust-analyzer/pull/19992)
108
189
109
190
### Rust Compiler Performance Triage
110
191
@@ -309,7 +390,15 @@ Please see the latest [Who's Hiring thread on r/rust](INSERT_LINK_HERE)
309
390
310
391
# Quote of the Week
311
392
312
-
<!-- QOTW goes here -->
393
+
394
+
395
+
> But after a few weeks, it compiled and the results surprised us. The code was 10x faster than our carefully tuned Kotlin implementation – despite no attempt to make it faster. To put this in perspective, we had spent years incrementally improving the Kotlin version from 2,000 to 3,000 transactions per second (TPS). The Rust version, written by Java developers who were new to the language, clocked 30,000 TPS.
396
+
>
397
+
> This was one of those moments that fundamentally shifts your thinking. Suddenly, the couple of weeks spent learning Rust no longer looked like a big deal, when compared with how long it’d have taken us to get the same results on the JVM. We stopped asking, “Should we be using Rust?” and started asking “Where else could Rust help us solve our problems?”
398
+
399
+
– [Dr. Werner Vogels on his blog](https://www.allthingsdistributed.com/2025/05/just-make-it-scale-an-aurora-dsql-story.html)
400
+
401
+
Thanks to [Brian Kung](https://users.rust-lang.org/t/twir-quote-of-the-week/328/1697) for the suggestion!
313
402
314
403
[Please submit quotes and vote for next week!](https://users.rust-lang.org/t/twir-quote-of-the-week/328)
0 commit comments