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.
This Week in Rust is openly developed on GitHub. If you find any errors in this week's issue, please submit a PR.
Updates from Rust Community
News & Blog Posts
- A Rust view on Effective Modern C++.
- The highs and lows of Rust (2017).
- Get Started with Rust, WebAssembly, and Webpack.
- Six months of rustc performance (2016-12 ~ 2017-05).
- Looping on a member variable without mutably borrowing self.
- Implementing Huffman algorithm in Rust.
- A whirlwind tour of rustdoc.
- Tock OS: RustConf tutorial preview and SITP retreat.
- rustup 1.5.0 is released with support for 'rust-toolchain' file.
- This week in Rust docs 61.
- This week in Redox 23.
- GSoC project: Making Redox self-hosting - status report 1.
- Announcing the Talk Help section. The "Talk Help" section in TRPLF is for discussing conference or meetup talks in all stages, from idea, over proposal to the post-talk feedback.
- Rusoto, an AWS SDK, has a codegen walkthrough that follows code generation from JSON files to Rust code. Codegen walkthrough, part two.
- [podcast] Request for Explanation #0 - What the hell. This week's topic is RFC 2005 "Match Ergonomics Using Default Binding Modes".
Friends of the Forest
Our community likes to recognize people who have made outstanding contributions to the Rust Project, its ecosystem, and its community. These people are 'friends of the forest'. The community team has been lax in making nominations for this on a regular basis, but we hope to get back on track!
Today's featured friend of the forest is Mark Simulacrum. As of Friday, June 23, Mark has made sure that all 2,634 open issues on the rust-lang/rust repo have a label! Thank you, Mark, for this heroic effort!
Crate of the Week
This week's crate is strum, a crate that allows you to derive stringify and parse operations for your enums. Thanks to lucab for the suggestion!
Submit your suggestions and votes for next week!
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.
- Rust libz blitz status update 2017-06-20. Contribution opportunities are available.
- rustup: Fix 'show' displaying UNC paths on windows.
- [easy] rustup: Fix 'show' when active toolchain is not installed.
- [easy] rustup: Add a reqwest backend to rustup.
- [easy] rustup: Teach hyper/rustls HTTP backends to resume partial downloads.
- walkdir: Add Error docs to methods that return Result.
- walkdir: Document why unwraps won't fail.
- walkdir: Link references to std in docs.
- walkdir: Correct errors in WalkDir type docs.
- walkdir: Document that
Iter
andIterFilterEntry
are the result of trait methods. - walkdir: Add links to other walkdir items in WalkDirIterator docs.
- walkdir: Add links to other walkdir items in Iter and IterFilterEntry docs.
- walkdir: Add links to other walkdir items in DirEntry docs.
- walkdir: Add example for content_first.
- rust-cookbook: Use
filter_entry
in walkdir examples. - [easy] rust-bindgen: Default to generating constified enums, rather than generating Rust enums.
- [less-easy] rust-bindgen: Rewrite
is_unsized
as either a graph traversal or fix-point analysis. - [less-easy] rust-bindgen: Rewrite
can_derive_debug
as either a graph traversal or fix-point analysis. - [less-easy] rust-bindgen: Rewrite
can_derive_copy[_in_array]
as either a graph traversal or fix-point analysis. - [less-easy] rust-bindgen: Rewrite
has_vtable
checks as either graph traversal or fix-point analysis.
If you are a Rust project owner and are looking for contributors, please submit tasks here.
Updates from Rust Core
94 pull requests were merged in the last week.
- MIR dataflow for borrows (this broke nightly, alas)
- make
break
break just the loop, not type inference (but break clippy in the process...) - enable
#[thread_local]
for Windows SyncSender
now implementsSync
- integrate jobserver for parallel codegen
compile_error!("...")
macro- implement
Display
,Debug
for *Guard
types wasm32-experimental-emscripten
target- more readable multiline message for
assert_eq!(..)
(also update test infrastructure and cargo for multiline messages) - allocator integration
- fix memory eating bug on name resolution
- avoid exponential blowup in
is_representable
- cherrypick LLVM stack coloring improvement
- avoid inlining unwind calls
- color for rustbuild errors
New Contributors
- Casey Rodarmor
- Chris MacNaughton
- Giles Cope
- Leonardo Yvens
- Nick Whitney
- slo
- Squirrel
Approved RFCs
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.
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. This week's FCPs are:
- [disposition: merge] Experimentally add coroutines to Rust.
- [disposition: merge] Tiered browser support policy for Rust's web content.
- [disposition: merge] Specify
#[repr(transparent)]
. - [disposition: merge] Conversions from
&mut T
to&Cell<T>
. - [disposition: merge] Stabilize drop order.
- [disposition: postpone] Allow
extern crate
to take a list of crates.
New RFCs
- Add
is_aligned
intrinsic. - Put the RFCs repo under license terms.
- Allow a break not only out of
loop
, but of labelled blocks with no loop. - Extend Rust target specification to follow more closely LLVM triple specification.
- Zero-Sized References.
Style RFCs
Style RFCs are part of the process for deciding on style guidelines for the Rust community and defaults for Rustfmt. The process is similar to the RFC process, but we try to reach rough consensus on issues (including a final comment period) before progressing to PRs. Just like the RFC process, all users are welcome to comment and submit RFCs. If you want to help decide what Rust code should look like, come get involved!
The RFC style is now the default style in Rustfmt - try it out and let us know what you think!
Issues in final comment period:
An interesting issue:
Good first issues:
We're happy to mentor these, please reach out to us in #rust-style if you'd like to get involved
Upcoming Events
- Jun 28. Boston Rust - Tutorial Bug-fixing Hackathon.
- Jun 28. OpenTechSchool Berlin - Rust Hack and Learn.
- Jun 28. Rust Community Team Meeting at #rust-community on irc.mozilla.org.
- Jun 28. Rust Documentation Team Meeting at #rust-docs on irc.mozilla.org.
- Jun 29. Rust release triage.
- Jun 29. Rust Durham, NC - Welcome to Rust! Introductions and Lightning Talks.
- Jun 3. Rust Prague Meetup.
- Jul 4. Rust Utrecht - Rust Workshop.
- Jul 5. Rust Atlanta - Grab a beer with fellow Rustaceans.
- Jul 5. Rust User Group Cologne - Live Coding.
- Jul 5. Rust Community Team Meeting at #rust-community on irc.mozilla.org.
- Jul 5. Rust Documentation Team Meeting at #rust-docs on irc.mozilla.org.
- Jul 7. Rust Toronto - Game Development in Rust.
- Jul 10. Seattle Rust Meetup.
- Jul 12. OpenTechSchool Berlin - Rust Hack and Learn.
- Jul 12. Rust Community Team Meeting at #rust-community on irc.mozilla.org.
- Jul 12. Rust Documentation Team Meeting at #rust-docs on irc.mozilla.org.
- Jul 13. Columbus Rust Society - Monthly Meetup.
- Jul 13. Rust release triage.
If you are running a Rust event please add it to the calendar to get it mentioned here. Email the Rust Community Team for access.
Rust Jobs
- Rust Software Engineer - Remote working available.
- Senior Research Engineer - Servo at Mozilla.
- Tor: Summer 2017 Internship to Create a Bridge Bandwidth Scanner.
- Student Research Assistant for developing Clippy in Karlsruhe (contact oliver.schneider \at kit.edu).
Tweet us at @ThisWeekInRust to get your job offers listed here!
Quote of the Week
Regarding the C++ discussion, when I started programming the only viable oss version control system was cvs. It was horrible, but better than nothing. Then subversion was created and it was like a breath of fresh air, because it did the same thing well. Then alternatives exploded and among them git emerged as this amazing, amazing game-changer because it changed the whole approach to version control, enabling amazing things.
To me, Rust is that git-like game-changer of systems programming languages because it changes the whole approach, enabling amazing things.
Thanks to Aleksey Kladov for the suggestion.