Skip to content

Commit 977f94f

Browse files
Merge branch 'main' into community-updates-629
2 parents 7911020 + f366c4e commit 977f94f

File tree

2 files changed

+55
-71
lines changed

2 files changed

+55
-71
lines changed

content/2024-10-16-this-week-in-rust.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,7 @@ and just ask the editors to select the category.
5050
* [An experiment in async Rust](https://ochagavia.nl/blog/an-experiment-in-async-rust/)
5151
* [Designing A Fast Concurrent Hash Table](https://ibraheem.ca/posts/designing-papaya/)
5252
* [Rethinking Builders… with Lazy Generics](https://geo-ant.github.io/blog/2024/rust-rethinking-builders-lazy-generics/)
53-
* [IPC in Rust](https://pranitha.rs/posts/rust-ipc-ping-pong/)
53+
* [IPC in Rust](https://pranitha.dev/posts/rust-ipc-ping-pong/)
5454
* [Serde Trait - Part 3: Deserialization](https://voelklmichael.github.io/Blog/serde-trait-part3.html)
5555
* [Memory for Nothing: Why Vec<usize> is (probably) a bad idea](https://pwy.io/posts/memory-for-nothing/)
5656
* [Upgrade the Logging in your Rust Tests](https://tylerjw.dev/posts/20241012-rust-logging-in-tests/)

draft/2025-12-10-this-week-in-rust.md

Lines changed: 54 additions & 70 deletions
Original file line numberDiff line numberDiff line change
@@ -41,28 +41,42 @@ and just ask the editors to select the category.
4141
* [Lessons learned from the Rust Vision Doc process](https://blog.rust-lang.org/2025/12/03/lessons-learned-from-the-rust-vision-doc-process/)
4242
* [Updating Rust's Linux musl targets to 1.2.5](https://blog.rust-lang.org/2025/12/05/Updating-musl-1.2.5/)
4343

44+
* [Making it easier to sponsor Rust contributors](https://blog.rust-lang.org/2025/12/08/making-it-easier-to-sponsor-rust-contributors/)
45+
4446
### Foundation
4547

4648
### Newsletters
49+
* [The Embedded Rustacean Issue #60](https://www.theembeddedrustacean.com/p/the-embedded-rustacean-issue-60)
4750

4851
### Project/Tooling Updates
4952
* [Yew 0.22 - For Real This Time](https://yew.rs/blog/2025/11/29/release-0-22)
5053
* [Ferrocene 25.11.0 now available!](https://ferrous-systems.com/blog/ferrocene-25-11-0/)
54+
* [YM2149-rs 0.8.0 — Cycle-accurate YM2149/AY-3-8910 chiptune ecosystem](https://ym2149-rs.org/)
55+
* [Duper's new superpowers!](https://duper.dev.br/blog/duper-s-new-superpowers.html)
56+
* [Announcing redis-rs 1.0.0 release](https://github.com/redis-rs/redis-rs/blob/main/version1.md)
57+
* [Announcing diesel-guard 0.2.0: Catch unsafe PostgreSQL migrations before they hit production](https://www.reddit.com/r/rust/comments/1phx68w/dieselguard_catch_unsafe_postgresql_migrations/)
58+
* [video] [Recording from the Rust Seoul meetup: Zia, a programming language that defines itself (written in Rust)](https://www.youtube.com/watch?v=LbFTP3pITWU)
5159

5260
### Observations/Thoughts
5361
* [Exploring deboa-macros: Ergonomic HTTP Client Macros for Rust](https://medium.com/@ararog/exploring-deboa-macros-ergonomic-http-client-macros-for-rust-d0c3df22e0a7)
5462
* [Fighting the Client Spaghetti Monster with Rust Traits](http://gnunicorn.org/writings/spaghetti-monster-clients-rust-traits-final-boss/)
5563
* [Rust unit testing: buffered file reading](https://jorgeortiz.dev/posts/rust_unit_testing_file_buf_reading/)
64+
* [Firecracker deep dive: How Rust and microVMs are revolutionizing cloud infrastructure](https://kerkour.com/firecracker-deep-dive-rust)
65+
* [iksemel rusted](https://thinkerf.blogspot.com/2025/12/iksemel-rusted.html)
66+
* [Postfix Macros and `let place`](https://nadrieril.github.io/blog/2025/12/09/postfix-macros-and-let-place.html)
67+
* [Should we get rid of clippy::manual_try_fold?](https://blog.veeso.dev/blog/en/should-we-get-rid-of-clippy-manual-try-fold/)
5668

5769
### Rust Walkthroughs
5870
* [Get in Line - superfast SPSC Queue](https://abhikja.in/blog/2025-12-07-get-in-line/)
5971
* [Emulating avx-512 intrinsics in Miri](https://trifectatech.org/blog/emulating-avx-512-intrinsics-in-miri/)
6072
* [How to speed up the Rust compiler in December 2025](https://nnethercote.github.io/2025/12/05/how-to-speed-up-the-rust-compiler-in-december-2025.html)
6173
* [From trees to graphs: speeding up vector search 10x with Hannoy](https://blog.kerollmops.com/from-trees-to-graphs-speeding-up-vector-search-10x-with-hannoy)
74+
* [series] [Part 1: Tokenization, Building an LLM From Scratch in Rust](https://www.tag1.com/white-paper/part1-tokenization-building-an-llm-from-scratch-in-rust/)
6275

6376
### Research
6477

6578
### Miscellaneous
79+
* [Pydantic: The Python Darling That Loves Rust](https://filtra.io/rust/interviews/pydantic-dec-25)
6680
* [video] [AWS re:Invent 2025 - Unleash Rust's potential on AWS (DEV307)](https://www.youtube.com/watch?v=buBBQ5mXAi8)
6781

6882
## Crate of the Week
@@ -81,46 +95,14 @@ If you are a feature implementer and would like your RFC to appear in this list,
8195
`call-for-testing` label to your RFC along with a comment providing testing instructions and/or
8296
guidance on which aspect(s) of the feature need testing.
8397

84-
<!-- If there are new CfT items this week, include:
85-
86-
[Repo Name](Repo URL)
87-
* [<Feature name>](<Feature URL>)
88-
* [Testing steps](<Testing Steps URL>)
89-
90-
- and make note in the item so the authors know to remove the `call-for-testing` label:
91-
This RFC will appear in the **Call for Testing** section of the next issue (#) of This Week in Rust (TWiR).
92-
You may remove the `call-for-testing` label. Please feel free to leave the `call-for-testing` label in place if you would like this RFC to appear again in another issue of TWiR.
93-
94-
- where `Repo Name` and `Repo URL` are one of:
95-
[Rust](https://github.com/rust-lang/rust/labels/call-for-testing),
96-
[Rust language RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing),
97-
[Cargo](https://github.com/rust-lang/cargo/labels/call-for-testing) or
98-
[Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing)
99-
100-
- and `Testing steps` points directly to the procedures the item wants users to exercise.
101-
102-
- For all `Repo Names` with no new CfT items this week: use (removing the repos for which new
103-
CfT items did appear, of course)
104-
10598
* *No calls for testing were issued this week by
10699
[Rust](https://github.com/rust-lang/rust/labels/call-for-testing),
107-
[Rust language RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing),
108-
[Cargo](https://github.com/rust-lang/cargo/labels/call-for-testing) or
100+
[Cargo](https://github.com/rust-lang/cargo/labels/call-for-testing),
101+
[Rust language RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing) or
109102
[Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing).*
110-
-->
111103

112104
[Let us know](https://github.com/rust-lang/this-week-in-rust/issues) if you would like your feature to be tracked as a part of this list.
113105

114-
### [RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing)
115-
116-
### [Rust](https://github.com/rust-lang/rust/labels/call-for-testing)
117-
118-
### [Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing)
119-
120-
If you are a feature implementer and would like your RFC to appear on the above list, add the new `call-for-testing`
121-
label to your RFC along with a comment providing testing instructions and/or guidance on which aspect(s) of the feature
122-
need testing.
123-
124106
## Call for Participation; projects and speakers
125107

126108
### CFP - Projects
@@ -153,61 +135,63 @@ If you are an event organizer hoping to expand the reach of your event, please s
153135

154136
### Rust Compiler Performance Triage
155137

156-
<!-- Perf results go here -->
138+
Overall result is negative this week, but both main regressions are on track to be addressed. No outstanding changes otherwise.
139+
140+
Triage done by **@panstromek**.
141+
Revision range: [eca9d93f..55495234](https://perf.rust-lang.org/?start=eca9d93f9057f9a48ff691bd65e7daf2f94c1b67&end=554952348a7dd13851f25789f6bb1061f45c4b60&absolute=false&stat=instructions%3Au)
142+
143+
**Summary**:
144+
145+
| (instructions:u) | mean | range | count |
146+
|:----------------------------------:|:-----:|:--------------:|:-----:|
147+
| Regressions ❌ <br /> (primary) | 0.4% | [0.1%, 4.3%] | 111 |
148+
| Regressions ❌ <br /> (secondary) | 0.4% | [0.1%, 2.2%] | 97 |
149+
| Improvements ✅ <br /> (primary) | -1.0% | [-1.3%, -0.7%] | 2 |
150+
| Improvements ✅ <br /> (secondary) | -0.2% | [-0.3%, -0.0%] | 9 |
151+
| All ❌✅ (primary) | 0.4% | [-1.3%, 4.3%] | 113 |
152+
153+
154+
3 Regressions, 2 Improvements, 3 Mixed; 3 of them in rollups
155+
30 artifact comparisons made in total
156+
157+
[Full report here](https://github.com/rust-lang/rustc-perf/blob/1e31d44e9db6e283552733052331af16e14e58e2/triage/2025/2025-12-08.md)
158+
157159

158160
### [Approved RFCs](https://github.com/rust-lang/rfcs/commits/master)
159161

160162
Changes to Rust follow the Rust [RFC (request for comments) process](https://github.com/rust-lang/rfcs#rust-rfcs). These
161163
are the RFCs that were approved for implementation this week:
162164

163-
<!-- Use either
164-
* [Item title](Item URL)
165-
- or
166-
* *No RFCs were approved this week.*
167-
-->
165+
* *No RFCs entered Final Comment Period this week.*
168166

169167
### Final Comment Period
170168

171169
Every week, [the team](https://www.rust-lang.org/team.html) announces the 'final comment period' for RFCs and key PRs
172170
which are reaching a decision. Express your opinions now.
173171

174172
#### Tracking Issues & PRs
175-
<!-- Either remove the group from the "No Items Entered Final Comment Period this week for" section
176-
and add the item(s) which entered Final comment period:
177-
##### [Group](Group URL)
178-
* [Item title](Item URL)
179-
- for `disposition-merge` `final-comment-period` items, or
180-
* [disposition: postpone]
181-
- for `disposition-postpone` `final-comment-period` items, or
182-
* [disposition: close]
183-
- for `disposition-close` `final-comment-period` items,
184-
* [disposition: unspecified]
185-
- when `disposition` is unspecified or ensure the group is a part of the
186-
"No Items Entered Final Comment Period this week for" section
173+
##### [Rust](https://github.com/rust-lang/rust/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
174+
* [Warn on codegen attributes on required trait methods](https://github.com/rust-lang/rust/pull/148756)
175+
* [NFC normalize lifetime identifiers](https://github.com/rust-lang/rust/pull/149192)
176+
* [don't normalize where-clauses when checking well-formedness](https://github.com/rust-lang/rust/pull/148477)
177+
178+
[Compiler Team](https://github.com/rust-lang/compiler-team/issues?q=label%3Amajor-change%20%20label%3Afinal-comment-period) [(MCPs only)](https://forge.rust-lang.org/compiler/mcp.html)
179+
* [Destabilise target-spec-json](https://github.com/rust-lang/compiler-team/issues/944)
180+
181+
[Rust RFCs](https://github.com/rust-lang/rfcs/labels/final-comment-period)
182+
* [RFC: `#[export_visibility = ...]` attribute](https://github.com/rust-lang/rfcs/pull/3834)
183+
187184
*No Items entered Final Comment Period this week for
188-
[Rust RFCs](https://github.com/rust-lang/rfcs/labels/final-comment-period),
189-
[Cargo](https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc),
190-
[Compiler Team](https://github.com/rust-lang/compiler-team/issues?q=label%3Amajor-change%20%20label%3Afinal-comment-period) [(MCPs only)](https://forge.rust-lang.org/compiler/mcp.html),
191-
[Language Team](https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+),
192-
[Language Reference](https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc),
193-
[Leadership Council](https://github.com/rust-lang/leadership-council/issues?q=state%3Aopen%20label%3Afinal-comment-period) or
194-
[Unsafe Code Guidelines](https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc).*
185+
[Cargo](https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc),
186+
[Language Team](https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+),
187+
[Language Reference](https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc),
188+
[Leadership Council](https://github.com/rust-lang/leadership-council/issues?q=state%3Aopen%20label%3Afinal-comment-period) or
189+
[Unsafe Code Guidelines](https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc).*
195190

196191
Let us know if you would like your PRs, Tracking Issues or RFCs to be tracked as a part of this list.
197-
-->
198192

199193
#### [New and Updated RFCs](https://github.com/rust-lang/rfcs/pulls)
200-
<!-- Use either
201-
* [Item title](Item URL)
202-
- for new items, or
203-
* [updated] [Item title](Item URL)
204-
- for updated items, or
205194
* *No New or Updated RFCs were created this week.*
206-
-->
207-
208-
<!-- Sample commit message
209-
Update CFT, FCP, MCP and RFC sections for TWiR-xxx
210-
-->
211195

212196
## Upcoming Events
213197

0 commit comments

Comments
 (0)