Skip to content

Commit f2e8645

Browse files
greyblakegreyblake
committed
Add nutype 0.6.0 to 2025-02-12-this-week-in-rust.md
1 parent 3a5691c commit f2e8645

File tree

1 file changed

+200
-0
lines changed

1 file changed

+200
-0
lines changed

‎draft/2025-02-12-this-week-in-rust.md‎

Lines changed: 200 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,200 @@
1+
Title: This Week in Rust $twir_issue_number
2+
Number: $twir_issue_number
3+
Date: $twir_issue_date
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://x.com/ThisWeekInRust) on X (formerly 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) and archives can be viewed at [this-week-in-rust.org](https://this-week-in-rust.org/).
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+
Want TWIR in your inbox? [Subscribe here](https://this-week-in-rust.us11.list-manage.com/subscribe?u=fd84c1c757e02889a9b08d289&id=0ed8b72485).
16+
17+
## Updates from Rust Community
18+
19+
<!--
20+
21+
Dear community contributors:
22+
Please read README.md for guidance on submissions.
23+
Each submitted link should be of the form:
24+
25+
* [Title of the Linked Page](https://example.com/my_article)
26+
27+
If you don't know which category to use, feel free to submit a PR anyway
28+
and just ask the editors to select the category.
29+
30+
-->
31+
32+
### Official
33+
34+
### Foundation
35+
36+
### Newsletters
37+
38+
### Project/Tooling Updates
39+
40+
* [Nutype 0.6.0 - newtype with guarantees supports const functions now](https://github.com/greyblake/nutype/releases/tag/v0.6.0)
41+
42+
### Observations/Thoughts
43+
44+
### Rust Walkthroughs
45+
46+
### Research
47+
48+
### Miscellaneous
49+
50+
## Crate of the Week
51+
52+
<!-- COTW goes here -->
53+
54+
[Please submit your suggestions and votes for next week][submit_crate]!
55+
56+
[submit_crate]: https://users.rust-lang.org/t/crate-of-the-week/2704
57+
58+
## Calls for Testing
59+
60+
An important step for RFC implementation is for people to experiment with the
61+
implementation and give feedback, especially before stabilization. The following
62+
RFCs would benefit from user testing before moving forward:
63+
64+
<!-- Calls for Testing go here, use this format:
65+
* [<RFC Topic>](<RFC URL>)
66+
* [Tracking Issue](<Tracking Issue URL>)
67+
* [Testing steps](<Testing Steps URL>)
68+
-->
69+
<!-- or if there are no new or updated RFCs this week, use: -->
70+
<!-- * *No New or Updated RFCs were created this week.* -->
71+
<!-- Remember to remove the `call-for-testing` label from the RFC so that the maintainer can signal for testers again, if desired. -->
72+
73+
### [RFCs](https://github.com/rust-lang/rfcs/issues?q=label%3Acall-for-testing)
74+
75+
### [Rust](https://github.com/rust-lang/rust/labels/call-for-testing)
76+
77+
### [Rustup](https://github.com/rust-lang/rustup/labels/call-for-testing)
78+
79+
If you are a feature implementer and would like your RFC to appear on the above list, add the new `call-for-testing`
80+
label to your RFC along with a comment providing testing instructions and/or guidance on which aspect(s) of the feature
81+
need testing.
82+
83+
## Call for Participation; projects and speakers
84+
85+
### CFP - Projects
86+
87+
Always wanted to contribute to open-source projects but did not know where to start?
88+
Every week we highlight some tasks from the Rust community for you to pick and get started!
89+
90+
Some of these tasks may also have mentors available, visit the task page for more information.
91+
92+
<!-- CFPs go here, use this format: * [project name - title of issue](URL to issue) -->
93+
<!-- * [ - ]() -->
94+
<!-- or if none - *No Calls for participation were submitted this week.* -->
95+
96+
If you are a Rust project owner and are looking for contributors, please submit tasks [here][guidelines] or through a [PR to TWiR](https://github.com/rust-lang/this-week-in-rust) or by reaching out on [X (formerly Twitter)](https://x.com/ThisWeekInRust) or [Mastodon](https://mastodon.social/@thisweekinrust)!
97+
98+
[guidelines]:https://github.com/rust-lang/this-week-in-rust?tab=readme-ov-file#call-for-participation-guidelines
99+
100+
### CFP - Events
101+
102+
Are you a new or experienced speaker looking for a place to share something cool? This section highlights events that are being planned and are accepting submissions to join their event as a speaker.
103+
104+
<!-- CFPs go here, use this format: * [**event name**](URL to CFP)| Date CFP closes in YYYY-MM-DD | city,state,country | Date of event in YYYY-MM-DD -->
105+
<!-- or if none - *No Calls for papers or presentations were submitted this week.* -->
106+
107+
If you are an event organizer hoping to expand the reach of your event, please submit a link to the website through a [PR to TWiR](https://github.com/rust-lang/this-week-in-rust) or by reaching out on [X (formerly Twitter)](https://x.com/ThisWeekInRust) or [Mastodon](https://mastodon.social/@thisweekinrust)!
108+
109+
## Updates from the Rust Project
110+
111+
<!-- Rust updates go here -->
112+
113+
### Rust Compiler Performance Triage
114+
115+
<!-- Perf results go here -->
116+
117+
### [Approved RFCs](https://github.com/rust-lang/rfcs/commits/master)
118+
119+
Changes to Rust follow the Rust [RFC (request for comments) process](https://github.com/rust-lang/rfcs#rust-rfcs). These
120+
are the RFCs that were approved for implementation this week:
121+
122+
<!-- Approved RFCs go here, use this format: * [Topic](URL) -->
123+
<!-- or if none were approved this week, use: * *No RFCs were approved this week.* -->
124+
<!-- * []() -->
125+
126+
<!--
127+
### [Approved Major Change Proposals (MCP)](https://forge.rust-lang.org/compiler/mcp.html)
128+
<!~~ MCPs occur infrequently, so this section is commented out by default. ~~>
129+
<!~~ MCPs which have been approved or rejected this week go here, use this format: * [major change accepted|rejected] [Topic](URL) ~~>
130+
-->
131+
132+
### Final Comment Period
133+
134+
Every week, [the team](https://www.rust-lang.org/team.html) announces the 'final comment period' for RFCs and key PRs
135+
which are reaching a decision. Express your opinions now.
136+
137+
#### [RFCs](https://github.com/rust-lang/rfcs/labels/final-comment-period)
138+
<!-- RFCs which have entered FCP go here, use this format: * [disposition: merge|close] [Topic](URL) -->
139+
<!-- or if none entered FCP this week, use: * *No RFCs entered Final Comment Period this week.* -->
140+
<!-- * [disposition: ] []() -->
141+
142+
#### Tracking Issues & PRs
143+
<!-- Tracking Issues which have entered FCP go here, use this format: * [disposition: merge|close] [Topic](URL) -->
144+
<!-- or if none entered FCP this week, use: -->
145+
<!-- * *No Tracking Issues or PRs entered Final Comment Period this week.* -->
146+
<!-- * [disposition: ] []() -->
147+
148+
##### [Rust](https://github.com/rust-lang/rust/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
149+
150+
##### [Cargo](https://github.com/rust-lang/cargo/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
151+
152+
##### [Language Team](https://github.com/rust-lang/lang-team/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc+)
153+
154+
##### [Language Reference](https://github.com/rust-lang/reference/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
155+
156+
##### [Unsafe Code Guidelines](https://github.com/rust-lang/unsafe-code-guidelines/issues?q=is%3Aopen+label%3Afinal-comment-period+sort%3Aupdated-desc)
157+
158+
#### [New and Updated RFCs](https://github.com/rust-lang/rfcs/pulls)
159+
<!-- New or updated RFCs go here, use this format: * [new|updated] [Topic](URL) -->
160+
<!-- or if there are no new or updated RFCs this week, use: -->
161+
<!-- * *No New or Updated RFCs were created this week.* -->
162+
<!-- * [new|updated] []() -->
163+
164+
## Upcoming Events
165+
166+
Rusty Events between $twir_issue_date - $twir_events_end_date 🦀
167+
168+
$twir_events_list
169+
170+
If you are running a Rust event please add it to the [calendar] to get
171+
it mentioned here. Please remember to add a link to the event too.
172+
Email the [Rust Community Team][community] for access.
173+
174+
[calendar]: https://www.google.com/calendar/embed?src=apd9vmbc22egenmtu5l6c5jbfc%40group.calendar.google.com
175+
[community]: mailto:[email protected]
176+
177+
## Jobs
178+
<!--
179+
180+
Rust Jobs:
181+
182+
TWiR has stopped featuring individual job postings. You can read more about this change here:
183+
184+
https://github.com/rust-lang/this-week-in-rust/issues/3412
185+
186+
-->
187+
188+
Please see the latest [Who's Hiring thread on r/rust](INSERT_LINK_HERE)
189+
190+
# Quote of the Week
191+
192+
<!-- QOTW goes here -->
193+
194+
[Please submit quotes and vote for next week!](https://users.rust-lang.org/t/twir-quote-of-the-week/328)
195+
196+
*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), [U007D](https://github.com/U007D), [joelmarcey](https://github.com/joelmarcey), [mariannegoldin](https://github.com/mariannegoldin), [bennyvasquez](https://github.com/bennyvasquez), [bdillo](https://github.com/bdillo)*
197+
198+
*Email list hosting is sponsored by [The Rust Foundation](https://foundation.rust-lang.org/)*
199+
200+
<small>[Discuss on r/rust](REDDIT_LINK_HERE)</small>

0 commit comments

Comments
 (0)