This post was published 258 days ago. The infomation described in this article may have changed.
Hello and welcome to another issue of This Week in Rust! Rust is a programming language empowering everyone to build reliable and efficient software. This is a weekly summary of its progress and community. Want something mentioned? Tag us at @ThisWeekInRust on Twitter or @ThisWeekinRust on mastodon.social, or send us a pull request. Want to get involved? We love contributions.
This week's crate is duplicate, a proc macro crate for easy parametric code duplication.
Thanks to Anton Fetisov for the suggestion!
Always wanted to contribute to open-source projects but did not know where to start? Every week we highlight some tasks from the Rust community for you to pick and get started!
Some of these tasks may also have mentors available, visit the task page for more information.
If you are a Rust project owner and are looking for contributors, please submit tasks here.
391 pull requests were merged in the last week
matchexpression in binary expression
Fnobligations with bound vars in the self type
&mut *xas mutating
suspicious_auto_trait_implslint for negative impls as well
.poll()not found on
dyn*and const closures in macros
Option::as_sliceto an always-sound implementation
Rc::into_inner, as a parallel to
TryFlattenUnordered: propagate base stream error
cargo install --gitmultiple packages with binaries found hint
cratereferences in blocks
manual_clampin const contexts
arithmetic_side_effectsfix false positive on shifts
cargoargs when running build scripts
A fairly mixed week, with several significant improvements and a few significant regressions. On average, this week saw a slight increase in compile times.
Triage done by @simulacrum. Revision range: 8f9e09ac..0058748
4 Regressions, 6 Improvements, 4 Mixed; 2 of them in rollups 39 artifact comparisons made in total
Changes to Rust follow the Rust RFC (request for comments) process. These are the RFCs that were approved for implementation this week:
Every week, the team announces the 'final comment period' for RFCs and key PRs which are reaching a decision. Express your opinions now.
An important step for RFC implementation is for people to experiment with the implementation and give feedback, especially before stabilization. The following RFCs would benefit from user testing before moving forward:
If you are a feature implementer and would like your RFC to appear on the above list, add the new
label to your RFC along with a comment providing testing instructions and/or guidance on which aspect(s) of the feature
Rusty Events between 2023-03-15 - 2023-04-12 🦀
Please see the latest Who's Hiring thread on r/rust
The Rust compiler is a thousand unit tests that you don't have to write
Thanks to Stephan Sokolow for the suggestion!
Email list hosting is sponsored by The Rust Foundation🏷️ Rust_feed