Skip to content
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Commit d93f500

Browse files
senekorsenekor
authoredMay 26, 2025··
Merge pull request #1614 from lqd/april-goals-updates
2025h1 project goals April update
2 parents c65edf7 + 40dc890 commit d93f500

File tree

1 file changed

+1505
-0
lines changed

1 file changed

+1505
-0
lines changed
 

‎content/Project-Goals-2025-April-Update.md

Lines changed: 1505 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,1505 @@
1+
+++
2+
path = "2025/05/26/april-project-goals-update"
3+
title = "April Project Goals Update"
4+
authors = ["Rémy Rakic"]
5+
6+
[extra]
7+
team = "the Goals team"
8+
team_url = "https://www.rust-lang.org/governance/teams/launching-pad#team-goals"
9+
+++
10+
11+
The Rust project is currently working towards a [slate of 40 project goals](https://rust-lang.github.io/rust-project-goals/2025h1/goals.html), with 3 of them designated as [Flagship Goals](https://rust-lang.github.io/rust-project-goals/2025h1/goals.html#flagship-goals). This post provides selected updates on our progress towards these goals (or, in some cases, lack thereof). The full details for any particular goal are available in its associated [tracking issue on the rust-project-goals repository](https://github.com/rust-lang/rust-project-goals/issues?q=is%3Aissue%20state%3Aopen%20label%3AC-tracking-issue).
12+
13+
## Flagship goals
14+
15+
<div style="display: flex;" class="mt2 mb3">
16+
<div style="flex: auto;"><a href='https://github.com/rust-lang/rust-project-goals/issues/105'><strong>Bring the Async Rust experience closer to parity with sync Rust</strong></a></div>
17+
<div style="flex: initial;"><progress value="5" max="34"></progress>
18+
</div>
19+
</div>
20+
<!-- markdown separator -->
21+
22+
**Why this goal?** This work continues our drive to improve support for async programming in Rust. In 2024H2 we stabilized async closures; explored the generator design space; and began work on the `dynosaur` crate, an experimental proc-macro to provide dynamic dispatch for async functions in traits. In 2025H1 [our plan](https://rust-lang.github.io/rust-project-goals/2025h1/async.html) is to deliver (1) improved support for async-fn-in-traits, completely subsuming the functionality of the [`async-trait` crate](https://crates.io/crates/async-trait); (2) progress towards sync and async generators, simplifying the creation of iterators and async data streams; (3) and improve the ergonomics of `Pin`, making lower-level async coding more approachable. These items together start to unblock the creation of the next generation of async libraries in the wider ecosystem, as progress there has been blocked on a stable solution for async traits and streams.
23+
24+
**What has happened?**
25+
26+
**Async fn in traits.** An FCP proposal to stabilize return type notation was started in <https://github.com/rust-lang/rust/pull/138424>. However, it is currently blocked on concerns that stabilizing it now will make it more difficult to ship Rust's next-generation trait solver.
27+
28+
**Async fn in dyn trait.** There have been discussions around next steps to support this in the language. More experimentation is needed, along with an initial RFC.
29+
30+
**dynosaur.** More breaking changes have landed and we expect to release v0.3 soon.
31+
32+
<!-- markdown separator -->
33+
34+
35+
<details>
36+
<summary>1 detailed update available.</summary>
37+
38+
<!-- this comment helps to convince the markdown parser to do the right thing -->
39+
40+
41+
<!-- this comment helps to convince the markdown parser to do the right thing -->
42+
43+
<a href="https://github.com/rust-lang/rust-project-goals/issues/105#issuecomment-2896086972">Comment by @tmandry posted on 2025-05-20:</a><br>
44+
45+
<blockquote>
46+
47+
<!-- this comment helps to convince the markdown parser to do the right thing -->
48+
49+
**Async fn in traits.** An FCP proposal to stabilize return type notation was started in <https://github.com/rust-lang/rust/pull/138424>. However, it is currently blocked on concerns that stabilizing it now will make it more difficult to ship Rust's next-generation trait solver.
50+
51+
**Async fn in dyn trait.** There have been discussions around next steps to support this in the language. More experimentation is needed, along with an initial RFC.
52+
53+
**dynosaur.** More breaking changes have landed and we expect to release v0.3 soon.
54+
55+
<!-- this comment helps to convince the markdown parser to do the right thing -->
56+
57+
</blockquote>
58+
59+
</details>
60+
61+
62+
63+
<br>
64+
<div style="display: flex;" class="mt2 mb3">
65+
<div style="flex: auto;"><a href='https://github.com/rust-lang/rust-project-goals/issues/263'><strong>Organize Rust All-Hands 2025</strong></a></div>
66+
<div style="flex: initial;"><progress value="18" max="28"></progress>
67+
</div>
68+
</div>
69+
<!-- markdown separator -->
70+
71+
**Why this goal?** May 15, 2025 marks the 10-year anniversary of Rust's 1.0 release; it also marks 10 years since the [creation of the Rust subteams](https://internals.rust-lang.org/t/announcing-the-subteams/2042). At the time [there were 6 Rust teams with 24 people in total](http://web.archive.org/web/20150517235608/http://www.rust-lang.org/team.html). There are now 57 teams with 166 people. In-person All Hands meetings are an effective way to help these maintainers get to know one another with high-bandwidth discussions. This year, the Rust project will be coming together for [RustWeek 2025](https://2025.rustweek.org), a joint event organized with [RustNL](https://2025.rustweek.org/about/). Participating project teams will use the time to share knowledge, make plans, or just get to know one another better. One particular goal for the All Hands is reviewing a draft of the [Rust Vision Doc](./rust-vision-doc.md), a document that aims to take stock of where Rust is and lay out high-level goals for the next few years.
72+
73+
**What has happened?** Things have been progressing smoothly. The work to prepare the schedule for the "pre all hands" and all hands has started with the teams. The COVID policy has been posted. Self-tests and CO₂ sensors have been received, as well as speaker-microphones to allow for remote participation.
74+
75+
<!-- markdown separator -->
76+
77+
78+
<details>
79+
<summary>3 detailed updates available.</summary>
80+
81+
<!-- this comment helps to convince the markdown parser to do the right thing -->
82+
83+
84+
<!-- this comment helps to convince the markdown parser to do the right thing -->
85+
86+
<a href="https://github.com/rust-lang/rust-project-goals/issues/263#issuecomment-2824692607">Comment by @m-ou-se posted on 2025-04-23:</a><br>
87+
88+
<blockquote>
89+
90+
<!-- this comment helps to convince the markdown parser to do the right thing -->
91+
92+
Update:
93+
94+
Below is the preliminary schedule for the "pre all hands" and all hands:
95+
96+
![Image](https://github.com/user-attachments/assets/9dd9aa14-1b37-478b-9071-3865ebac3994)
97+
98+
![Image](https://github.com/user-attachments/assets/4849caa8-c7af-4a9e-b1ee-75c1fafc7a6c)
99+
100+
![Image](https://github.com/user-attachments/assets/5888677e-3319-453c-9758-f8014954ebe6)
101+
102+
The last day has a lot of empty slots for now. I'm still working on filling those, but I'll leave a few empty slots to allow for flexibility during the event itself.
103+
104+
<!-- this comment helps to convince the markdown parser to do the right thing -->
105+
106+
</blockquote>
107+
108+
109+
<!-- this comment helps to convince the markdown parser to do the right thing -->
110+
111+
<a href="https://github.com/rust-lang/rust-project-goals/issues/263#issuecomment-2824770439">Comment by @m-ou-se posted on 2025-04-23:</a><br>
112+
113+
<blockquote>
114+
115+
<!-- this comment helps to convince the markdown parser to do the right thing -->
116+
117+
I published our covid policy: <https://rustweek.org/covid-policy-all-hands-and-unconf/>
118+
119+
And got us a ton of covid self-tests and Aranet4 CO₂ sensors:
120+
121+
![Image](https://github.com/user-attachments/assets/09f53af5-785b-4871-b7be-06f58b1b786d)
122+
![Image](https://github.com/user-attachments/assets/fdd79c8f-94bb-40b2-9cf9-ab949ebeb4e8)
123+
124+
<!-- this comment helps to convince the markdown parser to do the right thing -->
125+
126+
</blockquote>
127+
128+
129+
<!-- this comment helps to convince the markdown parser to do the right thing -->
130+
131+
<a href="https://github.com/rust-lang/rust-project-goals/issues/263#issuecomment-2824783540">Comment by @m-ou-se posted on 2025-04-23:</a><br>
132+
133+
<blockquote>
134+
135+
<!-- this comment helps to convince the markdown parser to do the right thing -->
136+
137+
For remote attendance, I got us a bunch of Jabra Speak2 75 conferencing speaker-microphones. They are battery powered and work out-of-the-box both over USB and Bluetooth on any platform.
138+
139+
I'll put them near the entrance for anyone to borrow for any of the meeting rooms.
140+
141+
![Image](https://github.com/user-attachments/assets/1669b50d-a60c-4ba0-8e82-9f403820d0a7)
142+
143+
<!-- this comment helps to convince the markdown parser to do the right thing -->
144+
145+
</blockquote>
146+
147+
</details>
148+
149+
150+
151+
<br>
152+
<div style="display: flex;" class="mt2 mb3">
153+
<div style="flex: auto;"><a href='https://github.com/rust-lang/rust-project-goals/issues/116'><strong>Stabilize tooling needed by Rust for Linux</strong></a></div>
154+
<div style="flex: initial;"><progress value="12" max="26"></progress>
155+
</div>
156+
</div>
157+
<!-- markdown separator -->
158+
159+
**Why this goal?** This goal continues our work from 2024H2 in supporting the [experimental support for Rust development in the Linux kernel][RFL.com]. Whereas in 2024H2 we were focused on stabilizing required language features, our focus in 2025H1 is stabilizing compiler flags and tooling options. We will (1) implement [RFC #3716] which lays out a design for ABI-modifying flags; (2) take the first step towards stabilizing [`build-std`](https://doc.rust-lang.org/cargo/reference/unstable.html#build-std) by [creating a stable way to rebuild core with specific compiler options](https://rust-lang.github.io/rust-project-goals/2025h1/build-std.html); (3) extending rustdoc, clippy, and the compiler with features that extract metadata for integration into other build systems (in this case, the kernel's build system).
160+
161+
[RFC #3716]: https://github.com/rust-lang/rfcs/pull/3716
162+
[RFL.com]: https://rust-for-linux.com/
163+
[RFL#2]: https://github.com/Rust-for-Linux/linux/issues/2
164+
165+
**What has happened?** The primary focus for this year is compiled flags, and we are continuing to push on the various compiler flags and things that are needed to support building RFL on stable (e.g., [RFC #3791] proposed adding `--crate-attr`, which permits injecting attributes into crates externally to allow the Kernel's build process to add things like `#![no_std]` so they don't have to be inserted manually into every file; MCPs for ABI flags like [`retpoline`](https://github.com/rust-lang/compiler-team/issues/868) and [`harden-sls`](https://github.com/rust-lang/compiler-team/issues/869) and [implementation of `-Zindirect-branch-cs-prefix`](https://github.com/rust-lang/rust/pull/140740)). A number of issues had minor design questions (how to manage clippy configuration; best approach for rustdoc tests) and we plan to use the RustWeek time to hash those out.
166+
167+
We are also finishing up some of the work on language items. We have had one stabilization of lang features needed by Rust for Linux ([`asm_goto` syntax](https://blog.rust-lang.org/2025/05/15/Rust-1.87.0/#asm-jumps-to-rust-code)). The trickiest bit here is arbitrary self types, where we encountered a concern relating to pin and are still [discussing the best resolution](https://rust-lang.zulipchat.com/#narrow/channel/425075-rust-for-linux/topic/2025-05-07.20meeting/near/516734641).
168+
169+
[RFC #3791]: https://github.com/rust-lang/rfcs/pull/3791
170+
171+
<!-- markdown separator -->
172+
173+
174+
<details>
175+
<summary>2 detailed updates available.</summary>
176+
177+
<!-- this comment helps to convince the markdown parser to do the right thing -->
178+
179+
180+
<!-- this comment helps to convince the markdown parser to do the right thing -->
181+
182+
<a href="https://github.com/rust-lang/rust-project-goals/issues/116#issuecomment-2894303032">Comment by @ojeda posted on 2025-05-20:</a><br>
183+
184+
<blockquote>
185+
186+
<!-- this comment helps to convince the markdown parser to do the right thing -->
187+
188+
Update from our 2025-04-09 meeting ([full minutes](https://hackmd.io/@rust-lang-team/rkqdLEER1l)):
189+
190+
- Some progress on `arbitrary_self_types`. In particular, decided to do with respect to pin and other related cases.
191+
192+
- `asm_goto` is solved, apart from output operands. For `asm_const`, <https://github.com/rust-lang/rust/pull/138618> is nominated.
193+
194+
- ABI-modifying compiler flags: some PRs waiting review, e.g. <https://github.com/rust-lang/rust/pull/138736>.
195+
196+
- `--crate-attr` RFC is up: <https://github.com/rust-lang/rfcs/pull/3791>.
197+
198+
- `-Zsanitize-kcfi-arity`'s implementation PR got merged: <https://github.com/rust-lang/rust/pull/138368>. If all is good from the Linux side, a stabilization PR will be sent.
199+
200+
- CFI `core::fmt` issue: <https://github.com/rust-lang/rust/issues/115199>.
201+
202+
- Discussion around `bindgen`, `repr(align)` and packed types. RFC nominated for lang discussion: <https://github.com/rust-lang/rfcs/pull/3718#issuecomment-2790654254>.
203+
204+
<!-- this comment helps to convince the markdown parser to do the right thing -->
205+
206+
</blockquote>
207+
208+
209+
<!-- this comment helps to convince the markdown parser to do the right thing -->
210+
211+
<a href="https://github.com/rust-lang/rust-project-goals/issues/116#issuecomment-2894308715">Comment by @ojeda posted on 2025-05-20:</a><br>
212+
213+
<blockquote>
214+
215+
<!-- this comment helps to convince the markdown parser to do the right thing -->
216+
217+
Update from our 2025-04-23 meeting ([full minutes](https://hackmd.io/@rust-lang-team/BJZ69jLkgx)):
218+
219+
- Naked functions were stabilized, which could see some use in the kernel.
220+
221+
- Lang discussed `#[repr(align)]` (the kernel is interested in, at least, the global one, i.e. `-Zmin-function-alignment=N`).
222+
223+
- `asm_const`: @nbdd0121 will reply on the latest review comments in the implementation PR: <https://github.com/rust-lang/rust/issues/128464>.
224+
225+
- `--crate-attr`: the author of the RFC (<https://github.com/rust-lang/rfcs/pull/3791>) is looking for a new owner. The RFC is in proposed FCP. Small updates to the text may be needed. Otherwise compiler probably wants to merge it. @Mark-Simulacrum to be pinged.
226+
227+
- Clippy configuration etc.: @flip1995 will be at RustWeek, the plan is to discuss it there.
228+
229+
- `rustdoc` extract doctests: @GuillaumeGomez and @ojeda plan to discuss it at RustWeek.
230+
231+
- `-Zsanitize-kcfi-arity`: waiting on the kernel side (`tc-build` support sent).
232+
233+
- CFI `core::fmt` issue: PR submitted: <https://github.com/rust-lang/rust/pull/139632>.
234+
235+
<!-- this comment helps to convince the markdown parser to do the right thing -->
236+
237+
</blockquote>
238+
239+
</details>
240+
241+
242+
<br>
243+
244+
## Goals looking for help
245+
246+
<div style="display: flex;" class="mt2 mb3">
247+
<div style="flex: auto;"><a href='https://github.com/rust-lang/rust-project-goals/issues/121'><strong>Promoting Parallel Front End</strong></a></div>
248+
<div style="flex: initial;"><progress value="0" max="3"></progress>
249+
</div>
250+
</div>
251+
<!-- markdown separator -->
252+
<!-- markdown separator -->
253+
254+
255+
<!-- markdown separator -->
256+
*Help wanted:* Help test the deadlock code in the [issue list](https://github.com/rust-lang/rust/labels/WG-compiler-parallel) and try to reproduce the issues. If you'd like to help, please post in [this goal's dedicated zulip topic](https://rust-lang.zulipchat.com/#narrow/channel/435869-project-goals/topic/Promoting.20Parallel.20Front.20End.20.28goals.23121.29/with/506292058).
257+
<!-- markdown separator -->
258+
259+
260+
<!-- markdown separator -->
261+
262+
<br>
263+
<div style="display: flex;" class="mt2 mb3">
264+
<div style="flex: auto;"><a href='https://github.com/rust-lang/rust-project-goals/issues/272'><strong>Stabilize public/private dependencies</strong></a></div>
265+
<div style="flex: initial;"><progress value="0" max="5"></progress>
266+
</div>
267+
</div>
268+
<!-- markdown separator -->
269+
<!-- markdown separator -->
270+
271+
272+
<!-- markdown separator -->
273+
*Help wanted:* T-compiler people to work on the blocking issues [#119428](https://github.com/rust-lang/rust/issues/119428) and [#71043](https://github.com/rust-lang/rust/issues/71043). If you'd like to help, please post in [this goal's dedicated zulip topic](https://rust-lang.zulipchat.com/#narrow/channel/435869-project-goals/topic/Stabilize.20public.2Fprivate.20dependencies.20.28goals.23272.29).
274+
<!-- markdown separator -->
275+
276+
277+
<!-- markdown separator -->
278+
279+
## Other goal updates
280+
281+
<div style="display: flex;" class="mt2 mb3">
282+
<div style="flex: auto;"><a href='https://github.com/rust-lang/rust-project-goals/issues/100'><strong>&quot;Stabilizable&quot; prototype for expanded const generics</strong></a></div>
283+
<div style="flex: initial;"><progress value="0" max="4"></progress>
284+
</div>
285+
</div>
286+
<!-- markdown separator -->
287+
288+
289+
290+
<!-- markdown separator -->
291+
292+
293+
<details>
294+
<summary>1 detailed update available.</summary>
295+
296+
<!-- this comment helps to convince the markdown parser to do the right thing -->
297+
298+
299+
<!-- this comment helps to convince the markdown parser to do the right thing -->
300+
301+
<a href="https://github.com/rust-lang/rust-project-goals/issues/100#issuecomment-2842025884">Comment by @BoxyUwU posted on 2025-04-30:</a><br>
302+
303+
<blockquote>
304+
305+
<!-- this comment helps to convince the markdown parser to do the right thing -->
306+
307+
I've a PR open to make resolving inherent assoc terms in item signatures not result in query cycles, this will be necessary for uses of inherent assoc consts in the type system under mgca. camelid is currently working on representing const items as aliases to type system consts rather than bodies like they currently are, this is necessary to implement normalization of const const aliases under mgca, it will also allow us to implement the core mgca check of const aliases in the type system being equal to valid const arguments, and also we'll be able to split out a full gca feature gate *without* that restriction.
308+
309+
The PR mentioned in the previous update to handle const aliases with inference variables correctly has turned into a bit of a rabbit hole. It turned out that there were *stable* issues around const evaluation and illformed constants resulting in ICEs so I've wound up trying to get those fixed and have been writing up a document explaining justification for a breaking change there.
310+
311+
<!-- this comment helps to convince the markdown parser to do the right thing -->
312+
313+
</blockquote>
314+
315+
</details>
316+
317+
318+
<div style="display: flex;" class="mt2 mb3">
319+
<div style="flex: auto;"><a href='https://github.com/rust-lang/rust-project-goals/issues/274'><strong>build-std</strong></a></div>
320+
<div style="flex: initial;"><progress value="0" max="4"></progress>
321+
</div>
322+
</div>
323+
<!-- markdown separator -->
324+
325+
326+
327+
<!-- markdown separator -->
328+
329+
330+
<details>
331+
<summary>1 detailed update available.</summary>
332+
333+
<!-- this comment helps to convince the markdown parser to do the right thing -->
334+
335+
336+
<!-- this comment helps to convince the markdown parser to do the right thing -->
337+
338+
<a href="https://github.com/rust-lang/rust-project-goals/issues/274#issuecomment-2857981933">Comment by @davidtwco posted on 2025-05-07:</a><br>
339+
340+
<blockquote>
341+
342+
<!-- this comment helps to convince the markdown parser to do the right thing -->
343+
344+
- We've started a regular biweekly sync call with upstream stakeholders in build-std from the lang, compiler and cargo teams where we discuss aspects of our tentative design or clarify constraints.
345+
- @adamgemmell has continued to draft our proposal for build-std, which we're discussing in our regular sync calls.
346+
- We're hosting a session at the All Hands next week to discuss build-std.
347+
348+
<!-- this comment helps to convince the markdown parser to do the right thing -->
349+
350+
</blockquote>
351+
352+
</details>
353+
354+
355+
<div style="display: flex;" class="mt2 mb3">
356+
<div style="flex: auto;"><a href='https://github.com/rust-lang/rust-project-goals/issues/104'><strong>Continue resolving &#x60;cargo-semver-checks&#x60; blockers for merging into cargo</strong></a></div>
357+
<div style="flex: initial;"><progress value="2" max="5"></progress>
358+
</div>
359+
</div>
360+
<!-- markdown separator -->
361+
362+
363+
364+
<!-- markdown separator -->
365+
366+
367+
<details>
368+
<summary>1 detailed update available.</summary>
369+
370+
<!-- this comment helps to convince the markdown parser to do the right thing -->
371+
372+
373+
<!-- this comment helps to convince the markdown parser to do the right thing -->
374+
375+
<a href="https://github.com/rust-lang/rust-project-goals/issues/104#issuecomment-2848816055">Comment by @obi1kenobi posted on 2025-05-03:</a><br>
376+
377+
<blockquote>
378+
379+
<!-- this comment helps to convince the markdown parser to do the right thing -->
380+
381+
We encountered some speedbumps this month.
382+
383+
TL;DR:
384+
- While working on `'static` and "outlives" bounds, we discovered Rust's ability to _imply_ bounds that are not stated explicitly at the definition site.
385+
- Implied bounds are load-bearing for SemVer; failure to take them into account will produce _both_ false-positives _and_ false-negatives.
386+
- While technical limitations make it infeasible for `cargo-semver-checks` to correctly deduce implied bounds, `rustc` has this capability internally.
387+
- We have [asked the rustdoc team](https://rust-lang.zulipchat.com/#narrow/channel/266220-t-rustdoc/topic/Show.20implied.20bounds.20in.20rustdoc.20JSON/near/515146429) to expose implied bounds in rustdoc JSON by using those `rustc` internal APIs.
388+
389+
There are some good news as well, though! While looking at the `#[target_feature]` attribute:
390+
- We discovered previously-undocumented SemVer hazards.
391+
- We [discovered a case of unsoundness](https://github.com/rust-lang/rust/issues/139368) when that attribute is used on trait methods.
392+
- With the help of contributors and the rustdoc team, rustdoc JSON began including additional information that will help future `cargo-semver-checks` versions catch those SemVer hazards.
393+
394+
<!-- this comment helps to convince the markdown parser to do the right thing -->
395+
396+
</blockquote>
397+
398+
</details>
399+
400+
401+
<div style="display: flex;" class="mt2 mb3">
402+
<div style="flex: auto;"><a href='https://github.com/rust-lang/rust-project-goals/issues/252'><strong>Declarative (&#x60;macro_rules!&#x60;) macro improvements</strong></a></div>
403+
<div style="flex: initial;"><progress value="3" max="29"></progress>
404+
</div>
405+
</div>
406+
<!-- markdown separator -->
407+
408+
409+
410+
<!-- markdown separator -->
411+
412+
413+
<!-- this comment helps to convince the markdown parser to do the right thing -->
414+
415+
<details>
416+
<summary>No detailed updates available.</summary>
417+
</details>
418+
419+
420+
<div style="display: flex;" class="mt2 mb3">
421+
<div style="flex: auto;"><a href='https://github.com/rust-lang/rust-project-goals/issues/253'><strong>Evaluate approaches for seamless interop between C++ and Rust</strong></a></div>
422+
<div style="flex: initial;"><progress value="2" max="6"></progress>
423+
</div>
424+
</div>
425+
<!-- markdown separator -->
426+
427+
428+
429+
<!-- markdown separator -->
430+
431+
432+
<!-- this comment helps to convince the markdown parser to do the right thing -->
433+
434+
<details>
435+
<summary>No detailed updates available.</summary>
436+
</details>
437+
438+
439+
<div style="display: flex;" class="mt2 mb3">
440+
<div style="flex: auto;"><a href='https://github.com/rust-lang/rust-project-goals/issues/107'><strong>Experiment with ergonomic ref-counting</strong></a></div>
441+
<div style="flex: initial;"><progress value="5" max="8"></progress>
442+
</div>
443+
</div>
444+
<!-- markdown separator -->
445+
446+
447+
448+
<!-- markdown separator -->
449+
450+
451+
<details>
452+
<summary>2 detailed updates available.</summary>
453+
454+
<!-- this comment helps to convince the markdown parser to do the right thing -->
455+
456+
457+
<!-- this comment helps to convince the markdown parser to do the right thing -->
458+
459+
<a href="https://github.com/rust-lang/rust-project-goals/issues/107#issuecomment-2786926399">Comment by @nikomatsakis posted on 2025-04-08:</a><br>
460+
461+
<blockquote>
462+
463+
<!-- this comment helps to convince the markdown parser to do the right thing -->
464+
465+
In reviewing <https://github.com/rust-lang/rust/pull/138628>, we realized that the tests were not behaving as expected because they were running in Rust 2015 which had distinct capture rules. My [suggestion](https://github.com/rust-lang/rust/pull/138628#pullrequestreview-2750344682) was to limit the `use` keyword (or at least use closures...) to Rust 2021 so as to avoid having to think about how it interacts with earlier capture rules (as well as potential migrations). I believe this follows from the Edition axiom that [Editions are meant to be adopted](https://rust-lang.github.io/rfcs/3085-edition-2021.html#editions-are-meant-to-be-adopted).
466+
467+
There is an interesting tension with [Rust should feel like one language](https://rust-lang.github.io/rfcs/3085-edition-2021.html#rust-should-feel-like-one-language). My feeling is that there is a missing tenet: the reason we do editions and not fine-grained features is because we wish to avoid combianotoric explosion, where odd combinations of features can lead to untested scenarios. But that is exactly what would be happening here if we allow `use` on older editions. So I think the rule should be that you make new features available on older editions *up until the point where they interact with something that changed* -- in this case, `use` closures interact with the closure capture rules which changed in Rust 2021, so we should limit this feature to Rust 2021 and newer.
468+
469+
Put another way, you should never have to go back and modify an edition migration to work differently. That suggestions you are attempting to push the feature too far back.
470+
471+
<!-- this comment helps to convince the markdown parser to do the right thing -->
472+
473+
</blockquote>
474+
475+
476+
<!-- this comment helps to convince the markdown parser to do the right thing -->
477+
478+
<a href="https://github.com/rust-lang/rust-project-goals/issues/107#issuecomment-2843027977">Comment by @spastorino posted on 2025-04-30:</a><br>
479+
480+
<blockquote>
481+
482+
<!-- this comment helps to convince the markdown parser to do the right thing -->
483+
484+
We've modified codegen so that we guarantee that `x.use` will do a copy if `X: Copy` is true after monomorphization. Before this change the desugaring to `clone` occurred only before monomorphization and hence it would call the `clone` method even for those instances where `X` is a `Copy` type. So with this modification we avoid such situation.
485+
486+
We are not working on convert `x.use` to a move rather than a clone if this is a last-use.
487+
488+
<!-- this comment helps to convince the markdown parser to do the right thing -->
489+
490+
</blockquote>
491+
492+
</details>
493+
494+
495+
<div style="display: flex;" class="mt2 mb3">
496+
<div style="flex: auto;"><a href='https://github.com/rust-lang/rust-project-goals/issues/109'><strong>Expose experimental LLVM features for GPU offloading</strong></a></div>
497+
<div style="flex: initial;"><progress value="2" max="4"></progress>
498+
</div>
499+
</div>
500+
<!-- markdown separator -->
501+
502+
503+
504+
<!-- markdown separator -->
505+
506+
507+
<!-- this comment helps to convince the markdown parser to do the right thing -->
508+
509+
<details>
510+
<summary>No detailed updates available.</summary>
511+
</details>
512+
513+
514+
<div style="display: flex;" class="mt2 mb3">
515+
<div style="flex: auto;"><a href='https://github.com/rust-lang/rust-project-goals/issues/110'><strong>Extend pubgrub to match cargo&#x27;s dependency resolution</strong></a></div>
516+
<div style="flex: initial;"><progress value="0" max="2"></progress>
517+
</div>
518+
</div>
519+
<!-- markdown separator -->
520+
521+
522+
523+
<!-- markdown separator -->
524+
525+
526+
<details>
527+
<summary>1 detailed update available.</summary>
528+
529+
<!-- this comment helps to convince the markdown parser to do the right thing -->
530+
531+
532+
<!-- this comment helps to convince the markdown parser to do the right thing -->
533+
534+
<a href="https://github.com/rust-lang/rust-project-goals/issues/110#issuecomment-2848617679">Comment by @Eh2406 posted on 2025-05-03:</a><br>
535+
536+
<blockquote>
537+
538+
<!-- this comment helps to convince the markdown parser to do the right thing -->
539+
540+
I will be giving [a talk at Rust-Week](https://rustweek.org/talks/jacob/) about the history that brought us to this project/goal. Aside from preparing for that talk I have not had time for this effort.
541+
542+
<!-- this comment helps to convince the markdown parser to do the right thing -->
543+
544+
</blockquote>
545+
546+
</details>
547+
548+
549+
<div style="display: flex;" class="mt2 mb3">
550+
<div style="flex: auto;"><a href='https://github.com/rust-lang/rust-project-goals/issues/254'><strong>Externally Implementable Items</strong></a></div>
551+
<div style="flex: initial;"><progress value="2" max="9"></progress>
552+
</div>
553+
</div>
554+
<!-- markdown separator -->
555+
556+
557+
558+
<!-- markdown separator -->
559+
560+
561+
<!-- this comment helps to convince the markdown parser to do the right thing -->
562+
563+
<details>
564+
<summary>No detailed updates available.</summary>
565+
</details>
566+
567+
568+
<div style="display: flex;" class="mt2 mb3">
569+
<div style="flex: auto;"><a href='https://github.com/rust-lang/rust-project-goals/issues/255'><strong>Finish the libtest json output experiment</strong></a></div>
570+
<div style="flex: initial;"><progress value="0" max="4"></progress>
571+
</div>
572+
</div>
573+
<!-- markdown separator -->
574+
575+
576+
577+
<!-- markdown separator -->
578+
579+
580+
<details>
581+
<summary>1 detailed update available.</summary>
582+
583+
<!-- this comment helps to convince the markdown parser to do the right thing -->
584+
585+
586+
<!-- this comment helps to convince the markdown parser to do the right thing -->
587+
588+
<a href="https://github.com/rust-lang/rust-project-goals/issues/255#issuecomment-2841981003">Comment by @epage posted on 2025-04-30:</a><br>
589+
590+
<blockquote>
591+
592+
<!-- this comment helps to convince the markdown parser to do the right thing -->
593+
594+
- Key developments:
595+
- Continued efforts to clean up the existing code
596+
- t-testing-devex has been working out where the crates should live in preparation for publishing them ([#t-testing-devex > crate ownership @ 💬](https://rust-lang.zulipchat.com/#narrow/channel/404371-t-testing-devex/topic/crate.20ownership/near/513724212))
597+
- Looking to build on the work done for `test-r` and `rustest` crates as they align with the long term vision
598+
- Blockers:
599+
- Help wanted:
600+
601+
<!-- this comment helps to convince the markdown parser to do the right thing -->
602+
603+
</blockquote>
604+
605+
</details>
606+
607+
608+
<div style="display: flex;" class="mt2 mb3">
609+
<div style="flex: auto;"><a href='https://github.com/rust-lang/rust-project-goals/issues/256'><strong>Implement Open API Namespace Support</strong></a></div>
610+
<div style="flex: initial;"><progress value="0" max="3"></progress>
611+
</div>
612+
</div>
613+
<!-- markdown separator -->
614+
615+
616+
617+
<!-- markdown separator -->
618+
619+
620+
<details>
621+
<summary>1 detailed update available.</summary>
622+
623+
<!-- this comment helps to convince the markdown parser to do the right thing -->
624+
625+
626+
<!-- this comment helps to convince the markdown parser to do the right thing -->
627+
628+
<a href="https://github.com/rust-lang/rust-project-goals/issues/256#issuecomment-2843397925">Comment by @eholk posted on 2025-04-30:</a><br>
629+
630+
<blockquote>
631+
632+
<!-- this comment helps to convince the markdown parser to do the right thing -->
633+
634+
@b-naber and I have been working on the rustc side of the implementation for this feature.
635+
636+
I merged <https://github.com/rust-lang/rust/pull/139647>, which adds the unstables `-Z namespaced-crates` option to the compiler and enables parsing of externs like `--extern foo::bar=libbar.rlib`. @b-naber has led the resolver changes and has a draft PR up at <https://github.com/rust-lang/rust/pull/140271>.
637+
638+
The implementation work has raised some [new concerns](https://github.com/rust-lang/rust/issues/122349#issuecomment-2832241624) about the overall direction, so work is ongoing to resolve those while continuing to make progress in the meantime.
639+
640+
<!-- this comment helps to convince the markdown parser to do the right thing -->
641+
642+
</blockquote>
643+
644+
</details>
645+
646+
647+
<div style="display: flex;" class="mt2 mb3">
648+
<div style="flex: auto;"><a href='https://github.com/rust-lang/rust-project-goals/issues/257'><strong>Implement restrictions, prepare for stabilization</strong></a></div>
649+
<div style="flex: initial;"><progress value="0" max="8"></progress>
650+
</div>
651+
</div>
652+
<!-- markdown separator -->
653+
654+
655+
656+
<!-- markdown separator -->
657+
658+
659+
<!-- this comment helps to convince the markdown parser to do the right thing -->
660+
661+
<details>
662+
<summary>No detailed updates available.</summary>
663+
</details>
664+
665+
666+
<div style="display: flex;" class="mt2 mb3">
667+
<div style="flex: auto;"><a href='https://github.com/rust-lang/rust-project-goals/issues/258'><strong>Improve state machine codegen</strong></a></div>
668+
<div style="flex: initial;"><progress value="1" max="6"></progress>
669+
</div>
670+
</div>
671+
<!-- markdown separator -->
672+
673+
674+
675+
<!-- markdown separator -->
676+
677+
678+
<!-- this comment helps to convince the markdown parser to do the right thing -->
679+
680+
<details>
681+
<summary>No detailed updates available.</summary>
682+
</details>
683+
684+
685+
<div style="display: flex;" class="mt2 mb3">
686+
<div style="flex: auto;"><a href='https://github.com/rust-lang/rust-project-goals/issues/126'><strong>Instrument the Rust standard library with safety contracts</strong></a></div>
687+
<div style="flex: initial;"><progress value="1" max="8"></progress>
688+
</div>
689+
</div>
690+
<!-- markdown separator -->
691+
692+
693+
694+
<!-- markdown separator -->
695+
696+
697+
<details>
698+
<summary>1 detailed update available.</summary>
699+
700+
<!-- this comment helps to convince the markdown parser to do the right thing -->
701+
702+
703+
<!-- this comment helps to convince the markdown parser to do the right thing -->
704+
705+
<a href="https://github.com/rust-lang/rust-project-goals/issues/126#issuecomment-2843622028">Comment by @celinval posted on 2025-04-30:</a><br>
706+
707+
<blockquote>
708+
709+
<!-- this comment helps to convince the markdown parser to do the right thing -->
710+
711+
We fixed issue <https://github.com/rust-lang/rust/issues/136925> that was blocking contract annotations on constant functions, which unblocks the initial PR to add some contract annotations in the standard library (<https://github.com/rust-lang/rust/pull/136578>). The PR currently triggers a CI failure which we are investigating.
712+
713+
<!-- this comment helps to convince the markdown parser to do the right thing -->
714+
715+
</blockquote>
716+
717+
</details>
718+
719+
720+
<div style="display: flex;" class="mt2 mb3">
721+
<div style="flex: auto;"><a href='https://github.com/rust-lang/rust-project-goals/issues/259'><strong>Making compiletest more maintainable: reworking directive handling</strong></a></div>
722+
<div style="flex: initial;"><progress value="0" max="5"></progress>
723+
</div>
724+
</div>
725+
<!-- markdown separator -->
726+
727+
728+
729+
<!-- markdown separator -->
730+
731+
732+
<details>
733+
<summary>1 detailed update available.</summary>
734+
735+
<!-- this comment helps to convince the markdown parser to do the right thing -->
736+
737+
738+
<!-- this comment helps to convince the markdown parser to do the right thing -->
739+
740+
<a href="https://github.com/rust-lang/rust-project-goals/issues/259#issuecomment-2843934346">Comment by @jieyouxu posted on 2025-05-01:</a><br>
741+
742+
<blockquote>
743+
744+
<!-- this comment helps to convince the markdown parser to do the right thing -->
745+
746+
Update (2025-05-01):
747+
748+
- Not much updates, recent compiletest changes were surrounding error annotation strictness/canonicalization and landing a new executor that doesn't depend on libtest, and I've mostly been involved in reviewing those.
749+
- Next planned changes are first to introduce some discipline into compiletest's error handling and contributor-facing diagnostics, because configuration and directive handling currently still has a ton of random panics all over the place.
750+
751+
<!-- this comment helps to convince the markdown parser to do the right thing -->
752+
753+
</blockquote>
754+
755+
</details>
756+
757+
758+
<div style="display: flex;" class="mt2 mb3">
759+
<div style="flex: auto;"><a href='https://github.com/rust-lang/rust-project-goals/issues/260'><strong>Metrics Initiative</strong></a></div>
760+
<div style="flex: initial;"><progress value="2" max="6"></progress>
761+
</div>
762+
</div>
763+
<!-- markdown separator -->
764+
765+
766+
767+
<!-- markdown separator -->
768+
769+
770+
<details>
771+
<summary>2 detailed updates available.</summary>
772+
773+
<!-- this comment helps to convince the markdown parser to do the right thing -->
774+
775+
776+
<!-- this comment helps to convince the markdown parser to do the right thing -->
777+
778+
<a href="https://github.com/rust-lang/rust-project-goals/issues/260#issuecomment-2810680086">Comment by @yaahc posted on 2025-04-16:</a><br>
779+
780+
<blockquote>
781+
782+
<!-- this comment helps to convince the markdown parser to do the right thing -->
783+
784+
Small progress update:
785+
786+
following the plan mentioned above plus some extra bits, I've implemented the following changes
787+
788+
* changed the json output to include the timestamp
789+
* changed the file naming to ensure uniqueness and not overwrite metrics for the same crate when built with different configurations
790+
* previously I was piggybacking on the hash used to name artifacts in the `.cargo` or `build` directories, which in the compiler is known as `extra_filename` and is configured by cargo, but it turns out this doesn't guarantee uniqueness
791+
* I've replaced this with the ["Strict Version Hash"](https://rustc-dev-guide.rust-lang.org/backend/libs-and-metadata.html?highlight=stable%20version%20hash#strict-version-hash) (SVH)
792+
* Doing so introduced an ICE when compiling some crates with incremental compilation enabled. I've since resolved this in <https://github.com/rust-lang/rust/pull/139502> and tested this version against the top 100 crates in the ecosystem and their dependencies to verify its working
793+
* I've been working with the infra team and they've setup a cloud instance of influxdb 3.0 and grafana, influxdb is setup, grafana in progress
794+
* I met with both libs and lang to discuss their needs related to the unstable feature usage metrics and metrics in general
795+
796+
Next Steps:
797+
* I've got everything setup for the docs.rs team to start gathering a sample dataset for which I will then upload to the server the infra team setup
798+
* update locally hosted PoC impl to work with recent changes to metrics files and naming and validate that it's working as expected
799+
* work on the queries for the grafana instance to setup a graph per feature showing usage over time
800+
* probably going to create fake usage data to with for this
801+
* on the side I'm also looking into how much work it would be to track relative usage of various library APIs under a single feature flag (e.g. <https://github.com/rust-lang/rust/issues/139911> tracking the specific functions used)
802+
* develop a better understanding of the expected cost of running an influxdb server
803+
804+
<!-- this comment helps to convince the markdown parser to do the right thing -->
805+
806+
</blockquote>
807+
808+
809+
<!-- this comment helps to convince the markdown parser to do the right thing -->
810+
811+
<a href="https://github.com/rust-lang/rust-project-goals/issues/260#issuecomment-2822723527">Comment by @yaahc posted on 2025-04-22:</a><br>
812+
813+
<blockquote>
814+
815+
<!-- this comment helps to convince the markdown parser to do the right thing -->
816+
817+
posting this here so I can link to it in other places, I've setup the basic usage over time chart using some synthesized data that just emulates quadraticly (is that a word?) increasing feature usage for my given feature over the course of a week (the generated data starts at 0 usages per day and ends at 1000 usages per day). This chart counts the usage over each day long period and charts those counts over a week. The dip at the end is the difference between when I generated the data, after which there is zero usage data, and when I queried it.
818+
819+
With this I should be ready to just upload the data once we've gathered it from docs.rs, all I need to do is polish and export the dashboards I've made from grafana to the rust-lang grafana instance, connect that instance to the rust-lang influxdb instance, and upload the data to influxdb once we've gathered it.
820+
821+
![Image](https://github.com/user-attachments/assets/4d3db7cf-04bc-400c-8791-ac10c402ccdf)
822+
823+
<!-- this comment helps to convince the markdown parser to do the right thing -->
824+
825+
</blockquote>
826+
827+
</details>
828+
829+
830+
<div style="display: flex;" class="mt2 mb3">
831+
<div style="flex: auto;"><a href='https://github.com/rust-lang/rust-project-goals/issues/122'><strong>Model coherence in a-mir-formality</strong></a></div>
832+
<div style="flex: initial;"><progress value="0" max="6"></progress>
833+
</div>
834+
</div>
835+
<!-- markdown separator -->
836+
837+
838+
839+
<!-- markdown separator -->
840+
841+
842+
<!-- this comment helps to convince the markdown parser to do the right thing -->
843+
844+
<details>
845+
<summary>No detailed updates available.</summary>
846+
</details>
847+
848+
849+
<div style="display: flex;" class="mt2 mb3">
850+
<div style="flex: auto;"><a href='https://github.com/rust-lang/rust-project-goals/issues/113'><strong>Next-generation trait solver</strong></a></div>
851+
<div style="flex: initial;"><progress value="0" max="4"></progress>
852+
</div>
853+
</div>
854+
<!-- markdown separator -->
855+
856+
857+
858+
<!-- markdown separator -->
859+
860+
861+
<details>
862+
<summary>1 detailed update available.</summary>
863+
864+
<!-- this comment helps to convince the markdown parser to do the right thing -->
865+
866+
867+
<!-- this comment helps to convince the markdown parser to do the right thing -->
868+
869+
<a href="https://github.com/rust-lang/rust-project-goals/issues/113#issuecomment-2846022991">Comment by @lcnr posted on 2025-05-01:</a><br>
870+
871+
<blockquote>
872+
873+
<!-- this comment helps to convince the markdown parser to do the right thing -->
874+
875+
We've made a lot of progress over the last 1.5 months. My change to opaque types in borrowck is pretty much done now: <https://github.com/rust-lang/rust/pull/139587>. It still needs some cleanup and an FCP to actually merge. We've already merged multiple cleanups on the way here.
876+
877+
We then started to test crater with the `-Znext-solver=globally`. @compiler-errors and me encountered and merged the fixes for 13 issues since then: <https://github.com/rust-lang/rust/pull/139791> <https://github.com/rust-lang/rust/pull/139798> <https://github.com/rust-lang/rust/pull/140236> <https://github.com/rust-lang/rust/pull/139900> <https://github.com/rust-lang/rust/pull/139828> <https://github.com/rust-lang/rust/pull/139774> <https://github.com/rust-lang/rust/pull/139762> <https://github.com/rust-lang/rust/pull/139789> <https://github.com/rust-lang/rust/pull/138845> <https://github.com/rust-lang/rust/pull/140306> <https://github.com/rust-lang/rust/pull/140305> <https://github.com/rust-lang/rust/pull/140276 <https://github.com/rust-lang/rust/pull/140302>. @Nadrieril was also helpful by minimizing an encountered issue.
878+
879+
With these improvements and multiple in-flight changes we're now at significantly less than 100 remaining regressions in the top 10000 crates and have started the first complete crater run today. We are using a single PR for all crater runs. Check out <https://github.com/rust-lang/rust/pull/133502> for the current status and the stack of in-flight changes.
880+
881+
<!-- this comment helps to convince the markdown parser to do the right thing -->
882+
883+
</blockquote>
884+
885+
</details>
886+
887+
888+
<div style="display: flex;" class="mt2 mb3">
889+
<div style="flex: auto;"><a href='https://github.com/rust-lang/rust-project-goals/issues/261'><strong>Nightly support for ergonomic SIMD multiversioning</strong></a></div>
890+
<div style="flex: initial;"><progress value="0" max="5"></progress>
891+
</div>
892+
</div>
893+
<!-- markdown separator -->
894+
895+
896+
897+
<!-- markdown separator -->
898+
899+
900+
<details>
901+
<summary>1 detailed update available.</summary>
902+
903+
<!-- this comment helps to convince the markdown parser to do the right thing -->
904+
905+
906+
<!-- this comment helps to convince the markdown parser to do the right thing -->
907+
908+
<a href="https://github.com/rust-lang/rust-project-goals/issues/261#issuecomment-2841895996">Comment by @veluca93 posted on 2025-04-30:</a><br>
909+
910+
<blockquote>
911+
912+
<!-- this comment helps to convince the markdown parser to do the right thing -->
913+
914+
Key developments: nothing substantial.
915+
916+
<!-- this comment helps to convince the markdown parser to do the right thing -->
917+
918+
</blockquote>
919+
920+
</details>
921+
922+
923+
<div style="display: flex;" class="mt2 mb3">
924+
<div style="flex: auto;"><a href='https://github.com/rust-lang/rust-project-goals/issues/262'><strong>Null and enum-discriminant runtime checks in debug builds</strong></a></div>
925+
<div style="flex: initial;"><progress value="1" max="3"></progress>
926+
</div>
927+
</div>
928+
<!-- markdown separator -->
929+
930+
931+
932+
<!-- markdown separator -->
933+
934+
935+
<!-- this comment helps to convince the markdown parser to do the right thing -->
936+
937+
<details>
938+
<summary>No detailed updates available.</summary>
939+
</details>
940+
941+
942+
<div style="display: flex;" class="mt2 mb3">
943+
<div style="flex: auto;"><a href='https://github.com/rust-lang/rust-project-goals/issues/114'><strong>Optimizing Clippy &amp; linting</strong></a></div>
944+
<div style="flex: initial;"><progress value="0" max="2"></progress>
945+
</div>
946+
</div>
947+
<!-- markdown separator -->
948+
949+
950+
951+
<!-- markdown separator -->
952+
953+
954+
<details>
955+
<summary>1 detailed update available.</summary>
956+
957+
<!-- this comment helps to convince the markdown parser to do the right thing -->
958+
959+
960+
<!-- this comment helps to convince the markdown parser to do the right thing -->
961+
962+
<a href="https://github.com/rust-lang/rust-project-goals/issues/114#issuecomment-2837910940">Comment by @blyxyas posted on 2025-04-29:</a><br>
963+
964+
<blockquote>
965+
966+
<!-- this comment helps to convince the markdown parser to do the right thing -->
967+
968+
Monthly update!
969+
970+
- In [the last monthly update](https://github.com/rust-lang/rust-project-goals/issues/114#issuecomment-2730435572) we saw the impact that [interning symbols](https://doc.rust-lang.org/nightly/nightly-rustc/rustc_span/symbol/struct.Symbol.html#method.intern) had on the program's performance. An effort to minimize this via a pre-interning symbol mechanism has been implemented in <https://github.com/rust-lang/rust-clippy/pull/14650> and <https://github.com/rust-lang/rust/pull/138682>
971+
972+
- We're phasing out the old ["str path"](https://doc.rust-lang.org/nightly/nightly-rustc/clippy_utils/fn.match_def_path.html) infrastructure into a new lazy alternative. <https://github.com/rust-lang/rust-clippy/pull/14705>
973+
974+
- We're currently in the effort to optimize some documentation lints that took up to 15% of the Clippy runtime (depending on how much documentation for each line of code you had.) See <https://github.com/rust-lang/rust-clippy/pull/14693>
975+
976+
- We've also been experimenting with lots of new possibilities, mainly on parallel lints. Although they currently are not performance improvements, there are some great hope put into them.
977+
978+
- Memory consumption and branch mispredictions are being monitored, they do not seem out of the ordinary.
979+
980+
- Monitoring cache misses and references, turns out that about 31% of cache references (792m found) are cache misses (253m found) in some benchmarks. We will check what's behind those numbers and if they can be improved.
981+
982+
This has been a great month for performance!
983+
984+
<!-- this comment helps to convince the markdown parser to do the right thing -->
985+
986+
</blockquote>
987+
988+
</details>
989+
990+
991+
<div style="display: flex;" class="mt2 mb3">
992+
<div style="flex: auto;"><a href='https://github.com/rust-lang/rust-project-goals/issues/106'><strong>Prepare const traits for stabilization</strong></a></div>
993+
<div style="flex: initial;"><progress value="5" max="14"></progress>
994+
</div>
995+
</div>
996+
<!-- markdown separator -->
997+
998+
999+
1000+
<!-- markdown separator -->
1001+
1002+
1003+
<details>
1004+
<summary>1 detailed update available.</summary>
1005+
1006+
<!-- this comment helps to convince the markdown parser to do the right thing -->
1007+
1008+
1009+
<!-- this comment helps to convince the markdown parser to do the right thing -->
1010+
1011+
<a href="https://github.com/rust-lang/rust-project-goals/issues/106#issuecomment-2841950116">Comment by @oli-obk posted on 2025-04-30:</a><br>
1012+
1013+
<blockquote>
1014+
1015+
<!-- this comment helps to convince the markdown parser to do the right thing -->
1016+
1017+
No updates
1018+
1019+
<!-- this comment helps to convince the markdown parser to do the right thing -->
1020+
1021+
</blockquote>
1022+
1023+
</details>
1024+
1025+
1026+
<div style="display: flex;" class="mt2 mb3">
1027+
<div style="flex: auto;"><a href='https://github.com/rust-lang/rust-project-goals/issues/121'><strong>Promoting Parallel Front End</strong></a></div>
1028+
<div style="flex: initial;"><progress value="0" max="3"></progress>
1029+
</div>
1030+
</div>
1031+
<!-- markdown separator -->
1032+
1033+
1034+
1035+
<!-- markdown separator -->
1036+
1037+
1038+
<!-- this comment helps to convince the markdown parser to do the right thing -->
1039+
1040+
<details>
1041+
<summary>No detailed updates available.</summary>
1042+
</details>
1043+
1044+
1045+
<div style="display: flex;" class="mt2 mb3">
1046+
<div style="flex: auto;"><a href='https://github.com/rust-lang/rust-project-goals/issues/264'><strong>Prototype a new set of Cargo &quot;plumbing&quot; commands</strong></a></div>
1047+
<div style="flex: initial;"><progress value="0" max="4"></progress>
1048+
</div>
1049+
</div>
1050+
<!-- markdown separator -->
1051+
1052+
1053+
1054+
<!-- markdown separator -->
1055+
1056+
1057+
<details>
1058+
<summary>3 detailed updates available.</summary>
1059+
1060+
<!-- this comment helps to convince the markdown parser to do the right thing -->
1061+
1062+
1063+
<!-- this comment helps to convince the markdown parser to do the right thing -->
1064+
1065+
<a href="https://github.com/rust-lang/rust-project-goals/issues/264#issuecomment-2841965738">Comment by @epage posted on 2025-04-30:</a><br>
1066+
1067+
<blockquote>
1068+
1069+
<!-- this comment helps to convince the markdown parser to do the right thing -->
1070+
1071+
- Key developments:
1072+
- The [cargo-plumbing repo](https://github.com/crate-ci/cargo-plumbing) was created to serve as the central place for collaboration on this effort
1073+
- @ashiskumarnaik posted crate-ci/cargo-plumbing#5 for the first plumbing command
1074+
- Blockers:
1075+
- Help wanted:
1076+
1077+
1078+
1079+
<!-- this comment helps to convince the markdown parser to do the right thing -->
1080+
1081+
</blockquote>
1082+
1083+
1084+
<!-- this comment helps to convince the markdown parser to do the right thing -->
1085+
1086+
<a href="https://github.com/rust-lang/rust-project-goals/issues/264#issuecomment-2851032075">Comment by @ojuschugh1 posted on 2025-05-05:</a><br>
1087+
1088+
<blockquote>
1089+
1090+
<!-- this comment helps to convince the markdown parser to do the right thing -->
1091+
1092+
Hi @epage , I am interested in working on this project. If you are still looking for someone.
1093+
1094+
<!-- this comment helps to convince the markdown parser to do the right thing -->
1095+
1096+
</blockquote>
1097+
1098+
1099+
<!-- this comment helps to convince the markdown parser to do the right thing -->
1100+
1101+
<a href="https://github.com/rust-lang/rust-project-goals/issues/264#issuecomment-2852224902">Comment by @epage posted on 2025-05-05:</a><br>
1102+
1103+
<blockquote>
1104+
1105+
<!-- this comment helps to convince the markdown parser to do the right thing -->
1106+
1107+
@ojuschugh1 iirc there is a GSoC proposal for this and we are waiting to hear whether it was accepted. If it was, it would likely involve coordinating with them on tasks.
1108+
1109+
<!-- this comment helps to convince the markdown parser to do the right thing -->
1110+
1111+
</blockquote>
1112+
1113+
</details>
1114+
1115+
1116+
<div style="display: flex;" class="mt2 mb3">
1117+
<div style="flex: auto;"><a href='https://github.com/rust-lang/rust-project-goals/issues/265'><strong>Publish first rust-lang-owned release of &quot;FLS&quot;</strong></a></div>
1118+
<div style="flex: initial;"><progress value="0" max="5"></progress>
1119+
</div>
1120+
</div>
1121+
<!-- markdown separator -->
1122+
1123+
1124+
1125+
<!-- markdown separator -->
1126+
1127+
1128+
<details>
1129+
<summary>1 detailed update available.</summary>
1130+
1131+
<!-- this comment helps to convince the markdown parser to do the right thing -->
1132+
1133+
1134+
<!-- this comment helps to convince the markdown parser to do the right thing -->
1135+
1136+
<a href="https://github.com/rust-lang/rust-project-goals/issues/265#issuecomment-2847874500">Comment by @JoelMarcey posted on 2025-05-02:</a><br>
1137+
1138+
<blockquote>
1139+
1140+
<!-- this comment helps to convince the markdown parser to do the right thing -->
1141+
1142+
Key Developments: The FLS repo has officially been transferred from Ferrous to the Rust Project. <https://github.com/rust-lang/fls> is now live.
1143+
1144+
Next step: Integrate the FLS with the Rust build system in order to support publishing within project processes.
1145+
1146+
Blockers: None yet. The build system integration could create some support requests, however.
1147+
1148+
<!-- this comment helps to convince the markdown parser to do the right thing -->
1149+
1150+
</blockquote>
1151+
1152+
</details>
1153+
1154+
1155+
<div style="display: flex;" class="mt2 mb3">
1156+
<div style="flex: auto;"><a href='https://github.com/rust-lang/rust-project-goals/issues/266'><strong>Publish first version of StableMIR on crates.io</strong></a></div>
1157+
<div style="flex: initial;"><progress value="0" max="6"></progress>
1158+
</div>
1159+
</div>
1160+
<!-- markdown separator -->
1161+
1162+
1163+
1164+
<!-- markdown separator -->
1165+
1166+
1167+
<details>
1168+
<summary>1 detailed update available.</summary>
1169+
1170+
<!-- this comment helps to convince the markdown parser to do the right thing -->
1171+
1172+
1173+
<!-- this comment helps to convince the markdown parser to do the right thing -->
1174+
1175+
<a href="https://github.com/rust-lang/rust-project-goals/issues/266#issuecomment-2842836236">Comment by @celinval posted on 2025-04-30:</a><br>
1176+
1177+
<blockquote>
1178+
1179+
<!-- this comment helps to convince the markdown parser to do the right thing -->
1180+
1181+
We have started the refactoring. @makai410 has moved all the existing code into a single crate and they have started moving things around.
1182+
1183+
<!-- this comment helps to convince the markdown parser to do the right thing -->
1184+
1185+
</blockquote>
1186+
1187+
</details>
1188+
1189+
1190+
<div style="display: flex;" class="mt2 mb3">
1191+
<div style="flex: auto;"><a href='https://github.com/rust-lang/rust-project-goals/issues/267'><strong>Research: How to achieve safety when linking separately compiled code</strong></a></div>
1192+
<div style="flex: initial;"><progress value="3" max="11"></progress>
1193+
</div>
1194+
</div>
1195+
<!-- markdown separator -->
1196+
1197+
1198+
1199+
<!-- markdown separator -->
1200+
1201+
1202+
<!-- this comment helps to convince the markdown parser to do the right thing -->
1203+
1204+
<details>
1205+
<summary>No detailed updates available.</summary>
1206+
</details>
1207+
1208+
1209+
<div style="display: flex;" class="mt2 mb3">
1210+
<div style="flex: auto;"><a href='https://github.com/rust-lang/rust-project-goals/issues/268'><strong>Run the 2025H1 project goal program</strong></a></div>
1211+
<div style="flex: initial;"><progress value="7" max="13"></progress>
1212+
</div>
1213+
</div>
1214+
<!-- markdown separator -->
1215+
1216+
1217+
1218+
<!-- markdown separator -->
1219+
1220+
1221+
<!-- this comment helps to convince the markdown parser to do the right thing -->
1222+
1223+
<details>
1224+
<summary>No detailed updates available.</summary>
1225+
</details>
1226+
1227+
1228+
<div style="display: flex;" class="mt2 mb3">
1229+
<div style="flex: auto;"><a href='https://github.com/rust-lang/rust-project-goals/issues/269'><strong>Rust Vision Document</strong></a></div>
1230+
<div style="flex: initial;"><progress value="0" max="4"></progress>
1231+
</div>
1232+
</div>
1233+
<!-- markdown separator -->
1234+
1235+
1236+
1237+
<!-- markdown separator -->
1238+
1239+
1240+
<!-- this comment helps to convince the markdown parser to do the right thing -->
1241+
1242+
<details>
1243+
<summary>No detailed updates available.</summary>
1244+
</details>
1245+
1246+
1247+
<div style="display: flex;" class="mt2 mb3">
1248+
<div style="flex: auto;"><a href='https://github.com/rust-lang/rust-project-goals/issues/275'><strong>rustc-perf improvements</strong></a></div>
1249+
<div style="flex: initial;"><progress value="0" max="7"></progress>
1250+
</div>
1251+
</div>
1252+
<!-- markdown separator -->
1253+
1254+
1255+
1256+
<!-- markdown separator -->
1257+
1258+
1259+
<details>
1260+
<summary>1 detailed update available.</summary>
1261+
1262+
<!-- this comment helps to convince the markdown parser to do the right thing -->
1263+
1264+
1265+
<!-- this comment helps to convince the markdown parser to do the right thing -->
1266+
1267+
<a href="https://github.com/rust-lang/rust-project-goals/issues/275#issuecomment-2857992478">Comment by @davidtwco posted on 2025-05-07:</a><br>
1268+
1269+
<blockquote>
1270+
1271+
<!-- this comment helps to convince the markdown parser to do the right thing -->
1272+
1273+
- @Jamesbarford has been working with @Kobzol to implement a database-backed job queueing mechanism, which will better scale to support multiple collectors and ends up being the key part of rustc-perf needing adapted to support multiple collectors.
1274+
- @Jamesbarford has also upstreamed tests for the existing queue ordering (rust-lang/rustc-perf#2072).
1275+
1276+
<!-- this comment helps to convince the markdown parser to do the right thing -->
1277+
1278+
</blockquote>
1279+
1280+
</details>
1281+
1282+
1283+
<div style="display: flex;" class="mt2 mb3">
1284+
<div style="flex: auto;"><a href='https://github.com/rust-lang/rust-project-goals/issues/118'><strong>Scalable Polonius support on nightly</strong></a></div>
1285+
<div style="flex: initial;"><progress value="10" max="18"></progress>
1286+
</div>
1287+
</div>
1288+
<!-- markdown separator -->
1289+
1290+
1291+
1292+
<!-- markdown separator -->
1293+
1294+
1295+
<details>
1296+
<summary>1 detailed update available.</summary>
1297+
1298+
<!-- this comment helps to convince the markdown parser to do the right thing -->
1299+
1300+
1301+
<!-- this comment helps to convince the markdown parser to do the right thing -->
1302+
1303+
<a href="https://github.com/rust-lang/rust-project-goals/issues/118#issuecomment-2850719303">Comment by @lqd posted on 2025-05-05:</a><br>
1304+
1305+
<blockquote>
1306+
1307+
<!-- this comment helps to convince the markdown parser to do the right thing -->
1308+
1309+
Here are the key developments for the month of April
1310+
1311+
- @amandasystems
1312+
- extracted a handful of PRs out of the gigantic placeholder rewrite PR, to make it easier to review and land
1313+
- <https://github.com/rust-lang/rust/pull/139960>, <https://github.com/rust-lang/rust/pull/139965>, and <https://github.com/rust-lang/rust/pull/140466>
1314+
- Tage
1315+
- continued experimenting and making progress with the early phase of the process, and making building constraints, and traversing them per loan, lazy
1316+
- started extracting some of that work for discussion, review, PRs, as well as writing reports for his masters thesis
1317+
- @lqd
1318+
- continued on improving the algorithm. We're now at a point where we have an approximation of the datalog algorithm, which handles our UI tests -- except one where control flow in a loop connects to regions that are live before and after the loop: this causes a false positive that our datalog implementation used to accept (via a more comprehensive but slower approach).
1319+
- we're currently discussing whether we can cut scope *here*, as this formulation accepts NLL problem case 3. We'll need to evaluate what limits this formulation imposes on expressiveness outside NLL problem case 3 and streaming iterators -- and whether it indeed has an easier path to becoming production ready. We'll also still try to see if it's possible to still improve the algorithm and avoid emitting errors on [issue 46589](https://github.com/rust-lang/rust/issues/46589), since we initially hoped to fix this one as well.
1320+
1321+
<!-- this comment helps to convince the markdown parser to do the right thing -->
1322+
1323+
</blockquote>
1324+
1325+
</details>
1326+
1327+
1328+
<div style="display: flex;" class="mt2 mb3">
1329+
<div style="flex: auto;"><a href='https://github.com/rust-lang/rust-project-goals/issues/271'><strong>Secure quorum-based cryptographic verification and mirroring for crates.io</strong></a></div>
1330+
<div style="flex: initial;"><progress value="0" max="12"></progress>
1331+
</div>
1332+
</div>
1333+
<!-- markdown separator -->
1334+
1335+
1336+
1337+
<!-- markdown separator -->
1338+
1339+
1340+
<!-- this comment helps to convince the markdown parser to do the right thing -->
1341+
1342+
<details>
1343+
<summary>No detailed updates available.</summary>
1344+
</details>
1345+
1346+
1347+
<div style="display: flex;" class="mt2 mb3">
1348+
<div style="flex: auto;"><a href='https://github.com/rust-lang/rust-project-goals/issues/119'><strong>Stabilize cargo-script</strong></a></div>
1349+
<div style="flex: initial;"><progress value="31" max="36"></progress>
1350+
</div>
1351+
</div>
1352+
<!-- markdown separator -->
1353+
1354+
1355+
1356+
<!-- markdown separator -->
1357+
1358+
1359+
<details>
1360+
<summary>1 detailed update available.</summary>
1361+
1362+
<!-- this comment helps to convince the markdown parser to do the right thing -->
1363+
1364+
1365+
<!-- this comment helps to convince the markdown parser to do the right thing -->
1366+
1367+
<a href="https://github.com/rust-lang/rust-project-goals/issues/119#issuecomment-2841974754">Comment by @epage posted on 2025-04-30:</a><br>
1368+
1369+
<blockquote>
1370+
1371+
<!-- this comment helps to convince the markdown parser to do the right thing -->
1372+
1373+
Key developments:
1374+
- @fee1-dead posted rust-lang/rust#140035 for compiler support for frontmatters (which supersedes rust-lang/rust#137193)
1375+
1376+
Blockers:
1377+
1378+
Help wanted:
1379+
1380+
<!-- this comment helps to convince the markdown parser to do the right thing -->
1381+
1382+
</blockquote>
1383+
1384+
</details>
1385+
1386+
1387+
<div style="display: flex;" class="mt2 mb3">
1388+
<div style="flex: auto;"><a href='https://github.com/rust-lang/rust-project-goals/issues/272'><strong>Stabilize public/private dependencies</strong></a></div>
1389+
<div style="flex: initial;"><progress value="0" max="5"></progress>
1390+
</div>
1391+
</div>
1392+
<!-- markdown separator -->
1393+
1394+
1395+
1396+
<!-- markdown separator -->
1397+
1398+
1399+
<!-- this comment helps to convince the markdown parser to do the right thing -->
1400+
1401+
<details>
1402+
<summary>No detailed updates available.</summary>
1403+
</details>
1404+
1405+
1406+
<div style="display: flex;" class="mt2 mb3">
1407+
<div style="flex: auto;"><a href='https://github.com/rust-lang/rust-project-goals/issues/270'><strong>SVE and SME on AArch64</strong></a></div>
1408+
<div style="flex: initial;"><progress value="2" max="16"></progress>
1409+
</div>
1410+
</div>
1411+
<!-- markdown separator -->
1412+
1413+
1414+
1415+
<!-- markdown separator -->
1416+
1417+
1418+
<details>
1419+
<summary>1 detailed update available.</summary>
1420+
1421+
<!-- this comment helps to convince the markdown parser to do the right thing -->
1422+
1423+
1424+
<!-- this comment helps to convince the markdown parser to do the right thing -->
1425+
1426+
<a href="https://github.com/rust-lang/rust-project-goals/issues/270#issuecomment-2857967334">Comment by @davidtwco posted on 2025-05-07:</a><br>
1427+
1428+
<blockquote>
1429+
1430+
<!-- this comment helps to convince the markdown parser to do the right thing -->
1431+
1432+
- We've resolved a handful of rounds of feedback on rust-lang/rust#137944 from @oli-obk, @lcnr and @fee1-dead; resolved issues from a crater run (bar one); and worked to decrease the performance regression.
1433+
- We've removed the constness parts of the patch to make it smaller and easier to review. Constness will come in a Part II.
1434+
- There's currently a -1% mean regression (min 0.1%, max 5.3%) that we're working to improve, but starting to run out of ideas. Regressions are just a consequence of the compiler having to prove more things with the addition of `MetaSized` bounds, rather than hot spots in newly introduced code.
1435+
- Given the large impact of the change, we ran a crater run and found three distinct issues, two have been fixed. The remaining issue is a overflow in a single niche crate which we're working out how we can resolve.
1436+
- We're largely just waiting on hearing from our reviewers what would be needed to see this change land.
1437+
- We've not made any changes to the Sized Hierarchy RFC, there's a small amount of discussion which will be responded to once the implementation has landed.
1438+
- We're working on changes to the SVE RFC which further clarifies that the language changes are decided by the Sized RFC and that the SVE RFC is only proposing the forever-unstable `repr(scalable)` attribute which are non-`const Sized` and lower to `vscale` in LLVM.
1439+
1440+
<!-- this comment helps to convince the markdown parser to do the right thing -->
1441+
1442+
</blockquote>
1443+
1444+
</details>
1445+
1446+
1447+
<div style="display: flex;" class="mt2 mb3">
1448+
<div style="flex: auto;"><a href='https://github.com/rust-lang/rust-project-goals/issues/273'><strong>Unsafe Fields</strong></a></div>
1449+
<div style="flex: initial;"><progress value="1" max="7"></progress>
1450+
</div>
1451+
</div>
1452+
<!-- markdown separator -->
1453+
1454+
1455+
1456+
<!-- markdown separator -->
1457+
1458+
1459+
<details>
1460+
<summary>1 detailed update available.</summary>
1461+
1462+
<!-- this comment helps to convince the markdown parser to do the right thing -->
1463+
1464+
1465+
<!-- this comment helps to convince the markdown parser to do the right thing -->
1466+
1467+
<a href="https://github.com/rust-lang/rust-project-goals/issues/273#issuecomment-2815572055">Comment by @jswrenn posted on 2025-04-18:</a><br>
1468+
1469+
<blockquote>
1470+
1471+
<!-- this comment helps to convince the markdown parser to do the right thing -->
1472+
1473+
**Key developments:** After the last lang team meeting, Ralf observed that the additive/subtractive dichotomy (and its attendant design concerns w.r.t. `Drop`) could be sidestepped, since a field type *already* cannot be put into an unsound-to-drop state without unsafe code. With this observation, we can reduce field safety tooling to two rules:
1474+
1475+
1. a field should be marked unsafe if it carries a safety invariant (of any kind)
1476+
2. a field marked `unsafe` is unsafe to use
1477+
1478+
The RFC now reflects this design and has more or less reached a fixed point. Ongoing discussion on the RFC is now mostly limited to weighing this design against a proposed alternative that mixes syntactically knobs and wrapper types. The RFC would benefit from formal review by @rust-lang/lang.
1479+
1480+
<!-- this comment helps to convince the markdown parser to do the right thing -->
1481+
1482+
</blockquote>
1483+
1484+
</details>
1485+
1486+
1487+
<div style="display: flex;" class="mt2 mb3">
1488+
<div style="flex: auto;"><a href='https://github.com/rust-lang/rust-project-goals/issues/123'><strong>Use annotate-snippets for rustc diagnostic output</strong></a></div>
1489+
<div style="flex: initial;"><progress value="0" max="13"></progress>
1490+
</div>
1491+
</div>
1492+
<!-- markdown separator -->
1493+
1494+
1495+
1496+
<!-- markdown separator -->
1497+
1498+
1499+
<!-- this comment helps to convince the markdown parser to do the right thing -->
1500+
1501+
<details>
1502+
<summary>No detailed updates available.</summary>
1503+
</details>
1504+
1505+

0 commit comments

Comments
 (0)
Please sign in to comment.