Hello and welcome to another issue of This Week in Rust! Rust is a systems language pursuing the trifecta: safety, concurrency, and speed. 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
News & Blog Posts
- Plans for the regex crate.
- Tokio's new internal semaphore based on intrusive lists.
- Rust async and the terrible, horrible, no good, very bad day.
- C++20 & Rust on static vs dynamic generics.
- Fast and simple Rust interner.
- Secure Rust guidelines.
- How I structure my apps (in Rust and other languages).
- Cheatsheet: Option (in Rust) vs Maybe (in Haskell).
- Two years with Rust.
- Reducing memory consumption in librsvg, part 3: slack space in Bézier paths.
- Inviting God's wrath with cursed Rust.
- Let’s write a Web Assembly interpreter (part 1).
- Descriptive statistics with NDArray.
- rust-analyzer changelog #17.
- Announcing Tokei 11: Now over 40–60% faster.
- Learn Rust building a toy JIRA clone.
- The original concept for the Rust logo.
Crate of the Week
This week's crates is flume, a fast multi-producer single-consumer channel.
Thanks to Vikrant 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!
Some of these tasks may also have mentors available, visit the task page for more information.
- Announcing Rust IPFS, and a call for contributors.
- The RustConf 2020 CFP is now open. We'd love to hear from you at RustConf!
- This Week in Rust is looking for a new maintainer.
If you are a Rust project owner and are looking for contributors, please submit tasks here.
Updates from Rust Core
380 pull requests were merged in the last week
- use generator resume arguments in the async/await lowering (async on core!)
- async: smaller and more correct generator codegen
- implement a feature for a sound specialization subset
- parser: recover on
for<'a> |...| bodyclosures
- resolve: print import chains on privacy errors
- resolve: do not resolve visibilities on proc macro definitions twice
- ast: compress
- fix type of const params in associated types
- revised span-to-lines conversion to produce an empty vec on
- rustc: use
- update the mir inline costs
- perf(dep_graph): avoid allocating a set on when the number reads are small
- don't unwind when hitting the macro expansion recursion limit
- miri: detect UB: overflow in
- allow calculating the layout behind a pointer
std::sync::Arccompatible with ThreadSanitizer
- proc_macro_harness: use item header spans for errors
BTreeMap: remove shared root
- hashbrown: use
NonNullfor the Bucket pointer
Changes to Rust follow the Rust RFC (request for comments) process. These are the RFCs that were approved for implementation 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.
No RFCs are currently in final comment period.
- [disposition: merge] Tracking issue for
- [disposition: merge] Allow obtaining &mut OsStr.
- [disposition: merge]
impl From<[T; N]> for Vec<T>.
- [disposition: merge] Implement Hash for Infallible.
- Access to traits' associated functions and constants from trait objects.
- Allow specifying dependencies for individual artifacts.
ForbiddenValuetrait to enable more optimizations.
- Mar 28. Stockholm, SE - Stockholm Rust - Rust Discord Hangout - Social Social Distancing.
- Apr 1. Johannesburg, ZA - Johannesburg Rust Meetup - Remote coffee and chat about Rust.
- Apr 6. Auckland, NZ - Rust AKL - Using C Libraries in Rust.
- Apr 9. San Diego, CA, US - San Diego Rust - April 2020 Meetup.
- Mar 31. Dallas, TX, US - Dallas Rust - Last Tuesday.
- Apr 1. Indianapolis, IN, US - Indy.rs - WebAssembly 101.
- Apr 9. Columbus, OH, US - Columbus Rust Society - Monthly Meeting.
Tweet us at @ThisWeekInRust to get your job offers listed here!
Quote of the Week
Rust is funny because in one sense it's hard and clunky. However, it's only ever precisely as hard and clunky as it needs to be. Everywhere something can be made more concise, or readable, or convenient, without sacrificing any control, it has been. Anytime something is hard or inconvenient, it's because the underlying domain really is exactly that hard or inconvenient.
Contrast this with other languages, which are often clunky when they don't need to be and/or "easy" when they shouldn't be.
Thanks to pitdicker for the suggestions!