Skip to content

Commit a6422fb

Browse files
nellshamrellnellshamrell
committed
adds draft for 492
Signed-off-by: Nell Shamrell <[email protected]>
1 parent 9f6612b commit a6422fb

File tree

1 file changed

+161
-0
lines changed

1 file changed

+161
-0
lines changed

‎draft/2023-04-26-this-week-in-rust.md

Lines changed: 161 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,161 @@
1+
Title: This Week in Rust 492
2+
Number: 492
3+
Date: 2023-04-26
4+
Category: This Week in Rust
5+
6+
Hello and welcome to another issue of *This Week in Rust*!
7+
[Rust](https://www.rust-lang.org/) is a programming language empowering everyone to build reliable and efficient software.
8+
This is a weekly summary of its progress and community.
9+
Want something mentioned? Tag us at [@ThisWeekInRust](https://twitter.com/ThisWeekInRust) on Twitter or [@ThisWeekinRust](https://mastodon.social/@thisweekinrust) on mastodon.social, or [send us a pull request](https://github.com/rust-lang/this-week-in-rust).
10+
Want to get involved? [We love contributions](https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md).
11+
12+
*This Week in Rust* is openly developed [on GitHub](https://github.com/rust-lang/this-week-in-rust).
13+
If you find any errors in this week's issue, [please submit a PR](https://github.com/rust-lang/this-week-in-rust/pulls).
14+
15+
## Updates from Rust Community
16+
17+
<!--
18+
19+
Dear community contributors:
20+
Please read README.md for guidance on submissions.
21+
Each submitted link should be of the form:
22+
23+
* [Title of the Linked Page](https://example.com/my_article)
24+
25+
If you don't know which category to use, feel free to submit a PR anyway
26+
and just ask the editors to select the category.
27+
28+
-->
29+
30+
### Official
31+
32+
### Foundation
33+
34+
### Newsletters
35+
36+
### Project/Tooling Updates
37+
38+
### Observations/Thoughts
39+
40+
### Rust Walkthroughs
41+
42+
### Research
43+
44+
### Miscellaneous
45+
46+
## Crate of the Week
47+
48+
<!-- COTW goes here -->
49+
50+
[Please submit your suggestions and votes for next week][submit_crate]!
51+
52+
[submit_crate]: https://users.rust-lang.org/t/crate-of-the-week/2704
53+
54+
## Call for Participation
55+
56+
Always wanted to contribute to open-source projects but did not know where to start?
57+
Every week we highlight some tasks from the Rust community for you to pick and get started!
58+
59+
Some of these tasks may also have mentors available, visit the task page for more information.
60+
61+
<!-- CFPs go here, use this format: * [project name - title of issue](link to issue) -->
62+
<!-- * [ - ]() -->
63+
64+
If you are a Rust project owner and are looking for contributors, please submit tasks [here][guidelines].
65+
66+
[guidelines]: https://users.rust-lang.org/t/twir-call-for-participation/4821
67+
68+
## Updates from the Rust Project
69+
70+
<!-- Rust updates go here -->
71+
72+
### Rust Compiler Performance Triage
73+
74+
<!-- Perf results go here -->
75+
76+
### [Approved RFCs](https://github.com/rust-lang/rfcs/commits/master)
77+
78+
Changes to Rust follow the Rust [RFC (request for comments) process](https://github.com/rust-lang/rfcs#rust-rfcs). These
79+
are the RFCs that were approved for implementation this week:
80+
81+
<!-- Approved RFCs go here, use this format: * [Topic](URL) -->
82+
<!-- or if none were approved this week, use: * *No RFCs were approved this week.* -->
83+
<!-- * []() -->
84+
85+
### Final Comment Period
86+
87+
Every week, [the team](https://www.rust-lang.org/team.html) announces the 'final comment period' for RFCs and key PRs
88+
which are reaching a decision. Express your opinions now.
89+
90+
#### [RFCs](https://github.com/rust-lang/rfcs/labels/final-comment-period)
91+
92+
<!-- RFCs which have entered FCP go here, use this format: * [disposition: merge|close] [Topic](URL) -->
93+
<!-- or if none entered FCP this week, use: * *No RFCs entered Final Comment Period this week.* -->
94+
<!-- * [disposition: ] []() -->
95+
96+
#### [Tracking Issues & PRs](https://github.com/rust-lang/rust/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
97+
98+
<!-- Tracking Issues which have entered FCP go here, use this format: * [disposition: merge|close] [Topic](URL) -->
99+
<!-- or if none entered FCP this week, use: * *No Tracking Issues or PRs entered Final Comment Period this week.* -->
100+
<!-- * [disposition: ] []() -->
101+
102+
### [New and Updated RFCs](https://github.com/rust-lang/rfcs/pulls)
103+
104+
<!-- New or updated RFCs go here, use this format: * [new|updated] [Topic](URL) -->
105+
<!-- or if there are no new or updated RFCs this week, use: * *No New or Updated RFCs were created this week.* -->
106+
<!-- * [new|updated] []() -->
107+
108+
### [Call for Testing](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing)
109+
An important step for RFC implementation is for people to experiment with the
110+
implementation and give feedback, especially before stabilization. The following
111+
RFCs would benefit from user testing before moving forward:
112+
113+
<!-- Calls for Testing go here, use this format:
114+
* [<RFC Topic>](<RFC URL>)
115+
* [Tracking Issue](<Tracking Issue URL>)
116+
* [Testing steps](<Testing Steps URL>)
117+
-->
118+
<!-- or if there are no new or updated RFCs this week, use: * *No New or Updated RFCs were created this week.* -->
119+
<!-- Remember to remove the `call-for-testing` label from the RFC so that the maintainer can signal for testers again, if desired. -->
120+
121+
If you are a feature implementer and would like your RFC to appear on the above list, add the new `call-for-testing`
122+
label to your RFC along with a comment providing testing instructions and/or guidance on which aspect(s) of the feature
123+
need testing.
124+
125+
## Upcoming Events
126+
127+
Rusty Events between 2023-04-26 - 2023-05-24 🦀
128+
129+
<!-- Events list goes here -->
130+
131+
If you are running a Rust event please add it to the [calendar] to get
132+
it mentioned here. Please remember to add a link to the event too.
133+
Email the [Rust Community Team][community] for access.
134+
135+
[calendar]: https://www.google.com/calendar/embed?src=apd9vmbc22egenmtu5l6c5jbfc%40group.calendar.google.com
136+
[community]: mailto:[email protected]
137+
138+
## Jobs
139+
<!--
140+
141+
Rust Jobs:
142+
143+
TWiR has stopped featuring individual job postings. You can read more about this change here:
144+
145+
https://github.com/rust-lang/this-week-in-rust/issues/3412
146+
147+
-->
148+
149+
Please see the latest [Who's Hiring thread on r/rust](INSERT_LINK_HERE)
150+
151+
# Quote of the Week
152+
153+
<!-- QOTW goes here -->
154+
155+
[Please submit quotes and vote for next week!](https://users.rust-lang.org/t/twir-quote-of-the-week/328)
156+
157+
*This Week in Rust is edited by: [nellshamrell](https://github.com/nellshamrell), [llogiq](https://github.com/llogiq), [cdmistman](https://github.com/cdmistman), [ericseppanen](https://github.com/ericseppanen), [extrawurst](https://github.com/extrawurst), [andrewpollack](https://github.com/andrewpollack), [U007D](https://github.com/U007D), [kolharsam](https://github.com/kolharsam), [joelmarcey](https://github.com/joelmarcey), [mariannegoldin](https://github.com/mariannegoldin), [bennyvasquez](https://github.com/bennyvasquez).*
158+
159+
*Email list hosting is sponsored by [The Rust Foundation](https://foundation.rust-lang.org/)*
160+
161+
<small>[Discuss on r/rust](REDDIT_LINK_HERE)</small>

0 commit comments

Comments
 (0)