This is the weekly Edition Status Update; it contains the state of the content areas surveyed this week. This is the third post in this series. You can read the second post here. This week will be the last status update before Preview 2.

Note: there has also been an important update to the Edition release schedule. We will have an extended beta period, meaning that the final release is now slated for 1.31 on December 6th.

Each content area below lists the blocking issues for the Preview 2 milestone described here, which is scheduled for 2018-08-02. In addition, some areas highlight important news or places where contribution is needed. You can track the full issue burndown on this spreadsheet.

General note

Please keep trying to migrate crates, the weirder the better!

Cargo-fix is now part of Cargo proper — no separate cargo install step needed.

Language stabilizations (@aturon)

Two features are in FCP for stabilization: Raw identifiers Attributes for tools

Still waiting for more feedback on: In-band lifetimes Will not ship in Preview 2, looking doubtful for Rust 2018 at all. Feedback is crucial here. Inferring T: 'x Blocked on adding a separate feature gate to one part of the feature.



First draft of web site content complete.

(News) ARM Cortex-M and Cortex-R related instructions added to coresimd . Permits removing asm! Will eventually be stabilized. See https://github.com/rust-lang-nursery/embedded-wg/issues/63 for more details https://doc.rust-lang.org/nightly/core/arch/arm/index.html Book work continues.

. IRR folks working on adding tests to thumb targets: https://github.com/rust-lang/rust/pull/52465 https://github.com/rust-lang-nursery/embedded-wg/issues/52 https://github.com/rust-lang-nursery/embedded-wg/issues/129#issuecomment-407087928

Blocking : panic implementation FCP. Need to work with team(s). Potential alternative: https://github.com/rust-lang/rfcs/pull/2492

: panic implementation FCP. Need to work with team(s). We’ll discuss maintenance and development of the embedded crates.io ecosystem as well as the restructuring of the rust-embedded GitHub organization in the next WG meeting. If you are interested or would like to help out, subscribe to https://github.com/rust-lang-nursery/embedded-wg/issues/130 and / or attend the meeting (date, time and place are in the linked issue).

Help Wanted We are looking for someone / people to help us write an RFC on stabilization of the ARM Cortex intrinsics in core::arch::arm . Details in https://github.com/rust-lang-nursery/embedded-wg/issues/63#issuecomment-408509178. We are replacing some of the f32 functions in libm with ports of newlib’s implementations to get better performance on devices that don’t support double precision floats. If you are interested in helping us with the port leave a comment in one of these issues.



Centril / Steve plan to knock out remaining issues for Preview 2.

Last week we got plenty of PRs with improvements and merged those. Please keep up reviews of the guide to polish it further.

Still waiting on stabilizations.

There are no Preview 2 blockers.

Still haven’t solved #[allow(clippy::somelint)] .

. Will be blocking on Clippy testing next cycle.

Need to rename some lints.

RFC still silent, oli-obk will try to talk to relevant folks.

Things are in great shape for Preview 2, both for diagnostics and performance. Niko will be writing a blog post soon giving a general update.

NLL will be part of Preview 2

CLI working group (@killercup)

We went through issues to assign people. Mostly docs work left

Clap 3 has a more detailed tracking issue/milestone News: 12 good issues for newcomers, help wanted! todo link (not all of these are on the milestone)

assert-rs is also moving towards stable release. See https://github.com/rust-lang-nursery/cli-wg/issues/40#issuecomment-407456460 for blockers.

is also moving towards stable release. Demo for generating man pages from clap definitions. Working on an example repository.

Markdown documentation for clap definitions: https://github.com/rust-clique/clap-md

killercup has looked into a WIP PR for issues already assigned to them.

We did some issue triage: Added https://github.com/rust-lang/cargo/issues/5778 to Preview 2. It lacks an assignee, but killercup and acrichto will discuss. Blockers: https://github.com/rust-lang/cargo/milestone/1 All cargo fix things: https://github.com/rust-lang/cargo/issues?q=is%3Aopen+is%3Aissue+label%3ACommand-fix

Might be good to make cargo fix without any arguments print a help message.

without any arguments print a help message. Good first issues: https://github.com/rust-lang/cargo/issues/5737 https://github.com/rust-lang/cargo/issues/5739 https://github.com/rust-lang/cargo/issues/5740



Down to 3 open lints for preview 2 which are all hygiene related and not essential for Preview 2, and will likely not make the preview. Not sure how critical the remaining issues are for the Edition; they’re somewhat theoretical

Should we abolish all mention of rust_2018_idioms or leave a stern warning about it probably not working well? Discussion on new issue.

Need input on https://github.com/ashleygwilliams/cargo-generate/issues?q=is%3Aissue+is%3Aopen+label%3A"Blocking+Rust+2018" from folks!

Published js-sys crate which was one of the big items for Preview 2

@ag_dubs is aiming to get wasm-pack 0.5.0 out for (roughly) Preview 2; Milestone is here.

Going to rename wasm-pack init into wasm-pack build and make it much more pleasant to build.

into and make it much more pleasant to build. fitzgen has a PR open to make the game of life tutorial the main body of the rust+wasm book, which is how we want it to be eventually, but we are holding off on landing the PR until we move the wasm-pack tutorial into the wasm-pack guide.

Help Wanted! Finishing js-sys so it has 100% complete bindings to JS globals: https://github.com/rustwasm/wasm-bindgen/issues/275 Help with the unreleased web-sys crate: https://github.com/rustwasm/wasm-bindgen/issues?q=is%3Aissue+is%3Aopen+label%3Aweb-sys https://rustwasm.github.io/wasm-bindgen/web-sys.html



Futures 0.3.0-alpha.1 is out!

The WG is being rebooted, with a major meeting this week to determine what to tackle next, now that futures 0.3.0-alpha.1 is out).

Notes from the WG kickoff meeting are here.

The WG will be working through the questions raised in the first meeting within the repo, and reconvene next week.