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
*[apply adjusts to pats and exprs when doing pat analysis](https://github.com/rust-lang/rust-analyzer/pull/20273)
185
+
*[disable tests in flycheck if `cfg.setTest` is set to false](https://github.com/rust-lang/rust-analyzer/pull/20271)
186
+
*[fix search of raw labels and lifetimes](https://github.com/rust-lang/rust-analyzer/pull/20262)
187
+
*[infer lifetimes for GATs in expression/pattern position](https://github.com/rust-lang/rust-analyzer/pull/20238)
130
188
131
189
### Rust Compiler Performance Triage
132
190
@@ -298,7 +356,11 @@ Please see the latest [Who's Hiring thread on r/rust](INSERT_LINK_HERE)
298
356
299
357
# Quote of the Week
300
358
301
-
<!-- QOTW goes here -->
359
+
> In a way, \[the\] borrow checker also makes interfaces simpler. The rules may be restrictive, but the same rules apply to everything everywhere. I can learn them once, and then know what to expect from every API using references. There are no exceptions in libraries that try to be clever. There are no exceptions for single-threaded programs. There are no exceptions for DLLs. There are no exceptions for programs built with -fpointers-go-sideways. It may be tricky like a game of chess, but I only need to consider the rules of the game, and not odd stuff like whether my opponent glued pieces to the chessboard.
360
+
361
+
– [Kornel Lesiński on hacker news](https://news.ycombinator.com/item?id=44620667)
362
+
363
+
Thanks to [danjl1100](https://users.rust-lang.org/t/twir-quote-of-the-week/328/1707) for the suggestion!
302
364
303
365
[Please submit quotes and vote for next week!](https://users.rust-lang.org/t/twir-quote-of-the-week/328)
0 commit comments