Skip to content

Commit c5cb073

Browse files
bennyvasquezbennyvasquez
authored
Merge branch 'master' into disable-debuginfo
2 parents 8b849ac + c39d7b4 commit c5cb073

File tree

1 file changed

+43
-51
lines changed

1 file changed

+43
-51
lines changed

‎draft/2025-05-21-this-week-in-rust.md

Lines changed: 43 additions & 51 deletions
Original file line numberDiff line numberDiff line change
@@ -41,14 +41,16 @@ and just ask the editors to select the category.
4141
### Project/Tooling Updates
4242

4343
### Observations/Thoughts
44-
44+
* [Evolution of Rust compiler errors](https://kobzol.github.io/rust/rustc/2025/05/16/evolution-of-rustc-errors.html)
45+
* [For your eyes only](https://bitfieldconsulting.com/posts/for-your-eyes-only)
4546
* [Disable debuginfo to improve Rust compile times](https://kobzol.github.io/rust/rustc/2025/05/20/disable-debuginfo-to-improve-rust-compile-times.html)
4647

4748
### Rust Walkthroughs
4849

4950
### Research
5051

5152
### Miscellaneous
53+
* [Scanner- The Team Accelerating Log Analysis With Rust](https://filtra.io/rust/interviews/scanner-may-25)
5254

5355
## Crate of the Week
5456

@@ -59,29 +61,16 @@ and just ask the editors to select the category.
5961
[submit_crate]: https://users.rust-lang.org/t/crate-of-the-week/2704
6062

6163
## Calls for Testing
62-
6364
An important step for RFC implementation is for people to experiment with the
64-
implementation and give feedback, especially before stabilization. The following
65-
RFCs would benefit from user testing before moving forward:
66-
67-
<!-- Calls for Testing go here, use this format:
68-
* [<RFC Topic>](<RFC URL>)
69-
* [Tracking Issue](<Tracking Issue URL>)
70-
* [Testing steps](<Testing Steps URL>)
71-
-->
72-
<!-- or if there are no new or updated RFCs this week, use: -->
73-
<!-- * *No New or Updated RFCs were created this week.* -->
74-
<!-- Remember to remove the `call-for-testing` label from the RFC so that the maintainer can signal for testers again, if desired. -->
75-
76-
### [RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing)
65+
implementation and give feedback, especially before stabilization.
7766

78-
### [Rust](https://github.com/rust-lang/rust/labels/call-for-testing)
67+
If you are a feature implementer and would like your RFC to appear in this list, add a
68+
`call-for-testing` label to your RFC along with a comment providing testing instructions and/or
69+
guidance on which aspect(s) of the feature need testing.
7970

80-
### [Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing)
81-
82-
If you are a feature implementer and would like your RFC to appear on the above list, add the new `call-for-testing`
83-
label to your RFC along with a comment providing testing instructions and/or guidance on which aspect(s) of the feature
84-
need testing.
71+
* *No calls for testing were issued this week by [Rust](https://github.com/rust-lang/rust/labels/call-for-testing),
72+
[Rust language RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing) or
73+
[Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing).*
8574

8675
## Call for Participation; projects and speakers
8776

@@ -115,54 +104,57 @@ If you are an event organizer hoping to expand the reach of your event, please s
115104

116105
### Rust Compiler Performance Triage
117106

118-
<!-- Perf results go here -->
107+
A relatively quiet week, likely caused by not that many PRs being merged as many contributors
108+
were at RustWeek and the All Hands event. There were several nice wins in trait solving;
109+
the benchmark suite now contains benchmarks that use the new trait solver, so we can now
110+
focus on optimizing its performance in the near future.
111+
112+
Triage done by **@kobzol**.
113+
114+
Revision range: [718ddf66..59372f2c](https://perf.rust-lang.org/?start=718ddf660e6a1802c39b4962cf7eaa4db57025ef&end=59372f2c81ba74554d9a71b12a4ed7f29adb33a2&absolute=false&stat=instructions%3Au)
115+
116+
**Summary**:
117+
| (instructions:u) | mean | range | count |
118+
|:----------------------------------:|:-----:|:--------------:|:-----:|
119+
| Regressions ❌ <br /> (primary) | 0.6% | [0.1%, 1.8%] | 25 |
120+
| Regressions ❌ <br /> (secondary) | 0.9% | [0.1%, 3.1%] | 23 |
121+
| Improvements ✅ <br /> (primary) | -0.3% | [-0.6%, -0.1%] | 33 |
122+
| Improvements ✅ <br /> (secondary) | -2.2% | [-9.2%, -0.1%] | 26 |
123+
| All ❌✅ (primary) | 0.1% | [-0.6%, 1.8%] | 58 |
124+
125+
2 Regressions, 5 Improvements, 3 Mixed; 3 of them in rollups
126+
41 artifact comparisons made in total
127+
128+
[Full report here](https://github.com/rust-lang/rustc-perf/blob/07f51987e0e9ca879a542ff365a4bac82d9c66f6/triage/2025-05-20.md).
119129

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

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

125-
<!-- Approved RFCs go here, use this format: * [Topic](URL) -->
126-
<!-- or if none were approved this week, use: * *No RFCs were approved this week.* -->
127-
<!-- * []() -->
128-
129-
<!--
130-
### [Approved Major Change Proposals (MCP)](https://forge.rust-lang.org/compiler/mcp.html)
131-
<!~~ MCPs occur infrequently, so this section is commented out by default. ~~>
132-
<!~~ MCPs which have been approved or rejected this week go here, use this format: * [major change accepted|rejected] [Topic](URL) ~~>
133-
-->
135+
* *No RFCs were approved this week.*
134136

135137
### Final Comment Period
136138

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

140-
#### [RFCs](https://github.com/rust-lang/rfcs/labels/final-comment-period)
141-
<!-- RFCs which have entered FCP go here, use this format: * [disposition: merge|close] [Topic](URL) -->
142-
<!-- or if none entered FCP this week, use: * *No RFCs entered Final Comment Period this week.* -->
143-
<!-- * [disposition: ] []() -->
144-
145142
#### Tracking Issues & PRs
146-
<!-- Tracking Issues which have entered FCP go here, use this format: * [disposition: merge|close] [Topic](URL) -->
147-
<!-- or if none entered FCP this week, use: -->
148-
<!-- * *No Tracking Issues or PRs entered Final Comment Period this week.* -->
149-
<!-- * [disposition: ] []() -->
150-
151143
##### [Rust](https://github.com/rust-lang/rust/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
144+
* [Tracking Issue for AVX512 intrinsics](https://github.com/rust-lang/rust/issues/111137)
145+
* [rustdoc: on mobile, make the sidebar full width and linewrap](https://github.com/rust-lang/rust/pull/139831)
152146

153-
##### [Cargo](https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
154-
155-
##### [Language Team](https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+)
156-
157-
##### [Language Reference](https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
147+
*No Items entered Final Comment Period this week for
148+
[Cargo](https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc),
149+
[Rust RFCs](https://github.com/rust-lang/rfcs/labels/final-comment-period),
150+
[Language Reference](https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc),
151+
[Language Team](https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+) or
152+
[Unsafe Code Guidelines](https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc).*
158153

159-
##### [Unsafe Code Guidelines](https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
154+
Let us know if you would like your PRs, Tracking Issues or RFCs to be tracked as a part of this list.
160155

161156
#### [New and Updated RFCs](https://github.com/rust-lang/rfcs/pulls)
162-
<!-- New or updated RFCs go here, use this format: * [new|updated] [Topic](URL) -->
163-
<!-- or if there are no new or updated RFCs this week, use: -->
164-
<!-- * *No New or Updated RFCs were created this week.* -->
165-
<!-- * [new|updated] []() -->
157+
* *No New or Updated RFCs were created this week.*
166158

167159
## Upcoming Events
168160

0 commit comments

Comments
 (0)