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.
- 4 years of Rust.
- The 2019 Rust event lineup.
- Understanding zero cost abstractions.
- Using Rust to scale Elixir for 11 million concurrent users.
- Rust in Avast.
- Evaluating pipelined rustc compilation.
- Analysis of various tricky Rust code.
- Get back some compile time from monomorphization.
- mem::uninitialized is deprecated.
- Shell completions in pure Rust.
- Creating C/C++ APIs in Rust.
- How to start Rust chat app.
- WebRender MVP ships in Firefox.
- Rust in Motion - a video series by Carol Nichols and Jake Goulding (requires purchase).
- Rust in Action - a book by Tim McNamara (early access, requires purchase).
This week we have two crates: memory-profiler, does what it says on the box. momo is a procedural macro that outlines generic conversions to reduce monomorphized code. Thanks to ehsanmok and llogiq for the suggestion!
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.
- Running a Rust Belt RustBridge.
- Submit your experience for newly await syntax.
- www.rust-lang.org: Frontend cleanup: Remove Skeleton.
If you are a Rust project owner and are looking for contributors, please submit tasks here.
240 pull requests were merged in the last week
- Move token tree related lexer state to a separate struct
- Stop using gensyms in HIR lowering
- Fix more escaping ReScopes
- Perform constant propagation into terminators
- Do some simple constant propagation in the
- Test interaction of unions with non-zero/niche-filling optimization
- Forego caching for all participants in cycles, apart from root node
- Remove the unstable and deprecated
- Stabilize core parts of
- Add entry-like methods to
- Add implementations of
lastin terms of
next_backon a bunch of
- Fix display of const generics in rustdoc
- rustup: Avoid blocking on
- rustc-guide: Add documentation about profile-guided optimization
- lint: convert
incoherent_fundamental_implsinto hard error
- clippy: Prevent symbocalypse
- crates.io: Fix performance regression on crate search
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.
Every week the team announces the 'final comment period' for RFCs and key PRs which are reaching a decision. Express your opinions now.
- [disposition: merge] Named custom cargo profiles.
- [disposition: merge] Stabilize RefCell::try_borrow_unguarded.
- [disposition: merge] Tracking issue for reversing the bit pattern in an integer.
- [disposition: merge] BufReader/Writer extension methods: is_empty, buffer.
- [disposition: merge] Bors policy question: Auto-reassignment on r+.
No new RFCs were proposed this week.
- Jun 5. Johannesburg, ZA - Johannesburg Rust Meetup - informal discussions on topics related to the language.
- May 23. Kharkiv, UA - PeerLab Kharkiv #Rust: Rust Success Stories.
- May 23. Paris, FR - Rust Paris meetup #45.
- May 26. St. Petersburg, RU - St. Petersburg Rust Meetup.
- May 29. Berlin, DE - OpenTechSchool Berlin - Rust Hack and Learn.
- May 28. Vilnius, LT - Rust Vilnius - Rust Safety and Distributed Consensus.
- Jun 6. Wroclaw, PL - Rust Wroclaw Meetup #11.
- May 27. Durham, NC, US - Triangle Rustaceans - Project Night & Lightning Talks.
- May 28. Dallas, TX, US - Dallas Rust - Last Tuesday.
- May 29. Vancouver, CA - Vancouver Rust meetup.
- May 29. Chicago, IL, US - Chicago Rust Meetup - Unsafe Rust.
- Jun 5. Atlanta, GA, US - Grab a beer with fellow Rustaceans.
- Jun 5. Indianapolis, IN, US - Indy.rs.
- Senior Software Engineer, Backend - Rust at Kraken, Berlin, DE or remote.
- Blockchain Runtime Engineer at Parity, Berlin, DE or remote.
Tweet us at @ThisWeekInRust to get your job offers listed here!
Just the presence of well integrated Algebraic Data Types (ADTs) makes an incredible amount of difference. They are used to represent errors in a meaningful and easy to understand way (
Result<T>), are used to show that a function may or may not return a meaningful value without needing a garbage value (
Option<T>), and the optional case can even be used to wrap a null pointer scenario in a safe way (
Option<Ref<T>>being the closest to a literal translation I think).
That’s just one small feature that permeates the language. Whatever the opposite of a death-of-a-thousand-cuts is, Rust has it.
Thanks to PrototypeNM1 for the suggestion!