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? Send me an email! Want to get involved? We love contributions.

This Week in Rust is openly developed on GitHub. If you find any errors or omissions in this week's issue, please submit a PR.

This week's edition was edited by: Brian Anderson.

What's cooking on master?

160 pull requests were merged in the last week.

Now you can follow breaking changes as they happen!

Breaking Changes

Prevent raw pointers from being used as explicit self. Probably nobody has ever tried to write such code, and the current implemented behavior is bonkers.

Other Changes

New Contributors

ben fleis

David Voit

Eli Friedman

frankamp

funkill

Johann Tuffe

joliv

Joshua Landau

Leo Correa

marcell

Marcel Müller

Matthew Astley

Nathan Long

Nick Fitzgerald

Russell McClellan

saml

simplex

swgillespie

Approved RFCs

New RFCs

Adjust default object bounds. This fixes some dumb rules that made it into 1.0, but is a breaking change that affects relatively little code.

Expand the std::net module.

Upcoming Events

If you are running a Rust event please add it to the calendar to get it mentioned here. Email Erick Tryzelaar or Brian Anderson for access.

Quote of the Week

text <Quxxy> I had a fun one in cargo script: there's currently no way in Rust to get a file's mtime and the system time in the same time format <Quxxy> (On Windows) <Quxxy> You can get one in UNIX time, the other in Windows time <Quxxy> Which have different scales and different epochs <Quxxy> Rust: Buy Your Own Damn Batteries; What Are You, A Communist?

Quxxy discovers Rust's stance toward the inclusion of batteries.

Thanks to cmr for the tip. Submit your quotes for next week!.