Hello and welcome to another issue of This Week in Rust! Rust is a systems language pursuing the trifecta: safe, concurrent, and fast. This is a weekly summary of its progress and community. Want something mentioned? Send me an email! Want to get involved? We love contributions.

It's been a long while since a TWiR, and I apologize for that. This TWiR is going to be much more abbreviated than usual. The normal pace will resume next week.

What's cooking on master?

There were 418 pull requests merged in the past two months, modulo any rollups (which are usually a combination of 10-20 pull requests).

Breaking Changes

88 commits contained breaking changes. Since this is a completely unreasonable number (and I'm sure ancient breaking changes aren't interesting), I'll just cover the last week's:

A bunch of changes happened to core::slice , including some trait renames. Most code shouldn't be affected by this, these traits are all in the prelude.

, including some trait renames. Most code shouldn't be affected by this, these traits are all in the prelude. A Duration type has been added, and many functions which logically take a duration have been changed to use it.

type has been added, and many functions which logically take a duration have been changed to use it. Imports and items are no longer allowed to shadow.

Other Changes

Far too many for me to list! Impressively, pcwalton has been knocking down backwards incompatible changes left and right. Currently, only 11 issues backwards incompatible language changes are tagged for 1.0. He has also implemented unboxed closures, fixed a bunch of soundness issues, a large portion of associated types, basic where clauses, lifetime elision, and various smaller issues.

There's been tons of library work, including stabilization, and cargo has really taken off.

New Contributors