This is the weekly Edition Status Update; it contains the state of the content areas surveyed this week. This is the second post in this series. You can read the first post here. This week we’re happy to announce that we were able to get status updates from every group.
Each content area 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.
- Please keep trying to migrate crates, the weirder the better!
- Focusing on:
- ICEs and correctness problems
- Edge cases for diagnostics
- Edge cases for performance or memory usage
- Making progress on those items
- Current list of issues is mostly assigned
- There are some ICEs and things yet to be investigated
- Meeting is at 19:30 UTC on Tuesday(s), and you can check the internals thread where we post updates and in particular issues to tackle.
- Thanks to lqd, pietroalbini and some others for crater run triage and assistance
- Clippy is in
rustup! So one issue down, just 2 left
- The RFC has been silent for a while, just needs a small patch and it should be ready.
- The other issue is
#[allow(clippy::foo)], but someone is working on it, so we’ll get it in a few weeks
- PR https://github.com/rust-lang/rust/pull/52264 was merged
Edition Guide (@steveklabnik)
- Current resources sufficient
- Work will be split up between steveklabnik, Centril, and @mark_simulacrum
- If you’d like to help out, feel free to give us feedback on the issue tracker, in particular we’d love input on the readability of the guide.
- No important news this week
- Preview 2 issues done
- RC issues blocked on stabilizations etc
- Need eyes on FCP for https://github.com/rust-lang/rust/issues/44489#issuecomment-398965881
- Feedback on https://japaric.github.io/discovery/ is always welcome and can be submitted to the issue tracker
- More tips like “I do $foo in C; what should I do in Rust” for https://github.com/rust-lang-nursery/embedded-wg/issues/126 are welcome.
- libm ported to rust, not yet available in standard distribution (on crates.io: https://crates.io/crates/libm)
- Originally had 4 things killercup wanted WG CLI to work on to make writing CLIs in Rust a somewhat coherent experience:
- Input (args, config files)
- Output (colors, logs, human vs machine output)
- Distribution (producing linux packages but also stuff like generating man pages)
- Testing (
- A lot of progress has already been made and published:
- Argument parsing (clap 3)
- Packaging (various efforts)
- Testing (@epage rewrote
- Other work has also happened, such as man page generation, but is not yet ready for use
- Two near-term strategies:
- Double down on ongoing efforts and push them over the finish line (requires killercup to work on stuff but way more heavily depends other people to be motivated to work on the right issues)
- Get prototypes going for the stuff we’ve only just designed
- killercup is inclined towards the former.
- Deliverable: A rough draft for a “writing a CLI app in rust in 15min” guide that showcases most of what killercup has mentioned
- Will try to work with some folks and see if we can integrate more other docs in a prominent place, e.g. https://crate-ci.github.io/
- Once we have some stuff that works, killercup will make sure to open a huge bunch of easy issues!
- clap and assert-rs already have a few easy issues
- Merging into Cargo
- Generally in good shape for Preview 2
- We need more testing!
- Migration lints should be reaching a pretty polished state
- Work on template stuff paused until
cargo generateis available (which it now is).
- Labeled under “Rust 2018 Preview 2”
- Generally: a lot of stuff is dependent on wasm-pack, which is also a bit in flux
- Going to talk to the WG about concrete goals for Preview 2
- Next wasm WG meeting: Thursday
- News Items:
wasm-bindgencrate has been a bit unstable as of late due to features being stabilized in the compiler. By next week we should be on smooth sailing again with only one unstable feature gate remaining (
use_extern_macros), thanks for your patience on nightly in the meantime!
- We’re very close to publishing a
js-syscrate, and help binding the remaining APIs would be greatly appreciated!
- Have you ever wished
cargo testwould “just work” for wasm? We may have an answer for you! Early adopters and feedback on this would be greatly appreciated!
- Work continues on a
web-syscrate for all browser APIs defined on the web, and if you’re interested we’d love your help in implementing more APIs!
rust_wasm_templaterepository is now compatible with the newly-published
cargo-generate, help us give it a spin!
Lang stabilizations (@aturon)
- aturon made a post about a roster of a few possible stabilizations for preview 2.
- We aim to stabilize these features. Thus, this is an excellent and the last opportunity to test them out and give feedback, particularly if you did not care for the features from the get go.
Networking WG (aturon)
- Attempting to reboot the WG
- Main goals for Preview 2:
- No news this week
- Solid progress this week, on track for Preview 2
- RFCs waiting on updates from nrc
- Down to just a single issue https://github.com/rust-lang-nursery/rls/issues/876
- In good shape for Preview 2
- A new version of the Rust (rls) plugin for VSCode has been released with some bugfixes.
- The VSCode plugin
- Clippy integration
- No change from last week
- Nothing pressing for Preview 2