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? Tweet us at @ThisWeekInRust or send us a pull request. Want to get involved? We love contributions.
Updates from Rust Community
- Rust Analyzer Changelog #92
- IntelliJ Rust Changelog #154
- GCC Rust Monthly Report #9 August 2021
- Bebop v2.3.0: Adding Rust support to Bebop serialization
- partial-borrow: derive macro for multiple (maybe mut) references to subsets/views of a struct
- Zellij 0.16.0 released: new UI, many bugfixes and more!
- Knurling-rs changelog #30
- SixtyFPS (GUI crate) weekly update
- This week in Fluvio #4: the programmable streaming platform
- This week in Datafuse #5
- [Tauri] Feature Freeze, Community Survey
- Game engine beginner - First look at Bevy - What is ECS and why should you care?
- An Alternative Syntax for Async Functions
- Development Cost of Porting TensorFlow Models to Pure Rust
- Rust Option and Result
- Asynchronous Rust: basic concepts
- Rust Visualized: Pointers as References
- Password auth in Rust, from scratch - Attacks and best practices
- Building an LC-3 virtual machine in Rust
- Combining Axum, Hyper, Tonic, and Tower for hybrid web/gRPC apps: Part 1
- [video] Getting started with Rust programming language 🦀 2021: 5. Refactoring the CLI app in Rust
- [video] Crust of Rust: async/await
- [video] Concurrency in Rust - Sharing State
- Struct Update Syntax in Rust
- htsget-rs: Bioinformatic file formats accessible to the web, 100% Rust, a GSoC2021 project wrap-up
- cold_iron: A Brief Introduction to Nanothaumaturgy
Crate of the Week
This week's crate is cargo-llvm-cov, a cargo subcommand for LLVM-based code coverage.
Thanks to Jacob Pratt for the suggestion.
Call for Participation
Always wanted to contribute to open-source projects but didn't know where to start? Every week we highlight some tasks from the Rust community for you to pick and get started!
- cdrs-tokio road to performance and testing
- RoaringBitmap/roaring-rs - The insert_range method does not properly handle boundary condition
- ockam-network/ockam - Ockam Vault for AWS (KMS/HSM) in Rust
- ockam-network/ockam - Ockam TCP Transport using smoltcp
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.
Updates from Rust Core
296 pull requests were merged in the last week
- fix debugger stepping behavior with match expressions
- improve liveness analysis for generators
- handle match statements with non exhaustive variants in closures
lower_spanfor catching all spans entering HIR
- PGO for LLVM builds on
- polonius: move to a fully hand-written parser to improve compile / iteration times
- warn about unreachable code following an expression with an uninhabited type
- normalize projections under binders
- stabilize and document
Saturatingtype (based on
- stdarch: update codegen for simd wasm intrinsics with LLVM 13
- futures: add
- cargo: show description of well known subcommands (fmt, clippy) in
- clippy: fix
- clippy: add
module_stylelint to style
- clippy: don't report function calls as unnecessary operation if used in array index
Rust Compiler Performance Triage
A very busy week with relatively even amounts of regressions and improvements (albeit with improvements outweighing regressions). The largest win was the use of profile-guided optimization (PGO) builds on x86_64 linux builds which brings fairly large improvements in real-world crates. There were 2 regressions that caused fairly large (~3.5%) regressions in real-world crates which need to be investigated.
Triage done by @rylev. Revision range: 33fdb..fe379
5 Regressions, 4 Improvements, 5 Mixed; 0 of them in rollups 56 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:
No RFCs were approved this week.
Final Comment Period
Every week the team announces the 'final comment period' for RFCs and key PRs which are reaching a decision. Express your opinions now.
- [disposition: close] Proposal: Else clauses for for and while loops
- [disposition: close] RFC: let-expression
- [disposition: merge] Scrape code examples from examples/ directory for Rustdoc
- [disposition: merge] Rust-lang crate ownership policy
- [disposition: merge] Partially stabilize array_methods
- [disposition: merge] Stabilize std::os::unix::fs::chroot
- [disposition: merge] Stabilize reserved prefixes
- [disposition: merge] stabilize disjoint capture in closures (RFC 2229)
- [disposition: merge] Stabilize try_reserve
- [disposition: merge] Support #[track_caller] on closures and generators
No new RFCs were proposed this week.
- September 2, 2021, Zurich, CH - Exciting new Rustdoc features landing in 1.55.0 - Hybrid Meetup (Livestream!) - Rust Zurich
- September 2, 2021, Berlin, DE - Rust Hack and Learn - Berline.rs
- September 7, 2021, Buffalo, NY, US - Buffalo Rust User Group, First Tuesdays - Buffalo Rust Meetup
- September 8, 2021, Denver, CO, US - Rust Q&A - Rust Denver
- September 14, 2021, Seattle, WA, US - Monthly Meetup - Seattle Rust Meetup
- September 15, 2021, Vancouver, BC, CA - Considering Rust - Vancouver Rust
- Backend Engineer - Rust - Core Backend (Remote)
- Backend Engineer, Kraken Futures - Rust (Remote)
- Senior Banking Engineer - Rust (Remote)
- Senior Software Engineer, Engineering Ops (London, UK, Milan, IT)
- Software Engineer, Engineering Ops (London, UK, Milan, IT)
- Engineering Lead, PayDirect (Milan, IT)
- Rust Software Engineer, PayDirect (London, UK, Milan, IT)
Tweet us at @ThisWeekInRust to get your job offers listed here!
Quote of the Week
Anyway: the standard library docs say "check the nomicon"
then the nomicon says "here is some advice and ultimately we don't know, maybe check UCG"
then UCG says "ultimately we don't know it's probably like this but there's no RFC yet"
then Ralf says "probably it should be allowed if the layout matches".
Thanks to Riccardo D'Ambrosio for the suggestion!