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
- Bisecting Rust compiler regressions with cargo-bisect-rustc.
- Stop worrying about blocking: the new async-std runtime, inspired by Go.
- From zero to main(): Bare metal Rust.
- WASM as a platform for abstraction.
- New gtk-rs release: Simplification and more of everything.
- Announcing Mio 0.7-alpha.1.
- Introduction to Rendology: A Glium-based rendering pipeline.
- The common Rust traits.
- Solving the Burger problem with Rust.
- Porting druid Rust widgets to PineTime smart watch.
- Relm tutorial.
- Why does rust seem to inspire people?
Crate of the Week
This week's crate is bstr, a string type for Rust that is not required to be valid UTF-8.
Thanks to Willi Kappler for the suggestions!
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.
No issues were proposed for CfP.
If you are a Rust project owner and are looking for contributors, please submit tasks here.
Updates from Rust Core
223 pull requests were merged in the last week
- revert stabilization of never type (sorry – llogiq)
whilein constants behind a feature flag
- make transparent enums more ordinary
- ensure a hard error on generic ZST constants whose body causes an eval error
- improve diagnostics and code for exhaustiveness of empty matches
- do not ICE on unnamed future
- remove the
- add ExactSizeIterator bound to return types
-Z print-type-sizes's handling of zero-sized fields
- track polonius in
- fix constant propagation for scalar pairs
unused_parenstriggers on macro by example code
- rustc: allow non-empty ParamEnv's in global trait select/eval caches
- remove uniform array move MIR passes
- chalk: remove depth getting passed around
- chalk: when truncating a goal, don't truncate the environment
- use first nonempty buffer in vectored I/O
- use deref target in Pin trait implementations
- improve code generated for
Ordtrait implementation for bool
- inline some common methods on
LinkedList: drop remaining items when drop panics
VecDeque: drop remaining items on destructor panic
- add a separate path for messages with no format arguments
- stabilize the
From<NonZero*>impls for wider
- add str::strip_prefix and str::strip_suffix
- cargo: emit error on
- rustup: improve preinstalled rust message
- docs.rs: fix panic viewing source if crate failed to build
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] Add IntoFuture trait and support for await.
- [disposition: merge] Add PartialEq and Eq to Cursor.
- [disposition: merge] Tracking issue for the
No new RFCs were proposed this week.
- Dec 20. Stuttgart, DE - Meetup Stuttgart - Rust Hack and Learn.
- Jan 8. Berlin, DE - OpenTechSchool Berlin - Rust Hack and Learn.
- Dec 23. Durham, NC, US - Triangle Rustaceans - Project Night & Lightning Talks.
- Dec 31. Dallas, TX, US - Dallas Rust - Last Tuesday.
- Jan 1. Indianapolis, IN, US - Indy.rs.
- Jan 8. Atlanta, GA, US - Grab a beer with fellow Rustaceans.
- Jan 8. Vancouver, BC, CA - Vancouver Rust meetup.
- Rust Developer for open-source work at Sigma Prime, Sydney, AU (Remote available).
- WebAssembly and Compiler Engineer at NEAR, multiple locations (Remote available).
- Rust Developer at WarnerMedia, US.
Tweet us at @ThisWeekInRust to get your job offers listed here!
Quote of the Week
Hey @rustlang folks, is there a comprehensive writeup/reference anywhere of how the formatting machinery (format!(), write!(), etc.) work? Specifically from an implementation perspective (wrt trait objects, recursion)?
It’s dark and ancient magic. I don’t think anyone knows it very well, never mind documentation
Thanks to mmmmib for the suggestion!