Subteam report: tools 2016-01-30
Highlights
This was a busy past few weeks for the tools in Rust, especially in the realm of Cargo!
- An initial port for powerpc64 and powerpc64le targets has been added.
- Static libraries and import libraries for MSVC have been renamed to have more conventional names on Windows.
- Binaries on Linux and BSDs now have the NX bit set. This brings these platforms in line with the behavior on Windows and OSX.
- A new
cargo initsubcommand has been implemented to initialize pre-existing Rust projects with Cargo configuration. - A new
cargo metadatasubcommand has been implemented to learn about a Cargo project through the CLI via JSON output. - The meaning of
cargo installas a plain command has been changed to install the current crate (e.g. the one at$PWD). - A new
project.publishkey in Cargo.toml has been added to indicate that a crate cannot be published to crates.io.
Dashboard
High priority issues
- Cargo Issue #782: Resolve errors are likely quite obscure
- Cargo Issue #942: Allow top-level overrides to be stored in the manifest
- Cargo Issue #1007:
Need ability to add dependencies based on
#[cfg()] - Cargo Issue #1098: Externally discover the source directories of dependencies?
- Cargo Issue #1251: Build dependency awareness
- Cargo Issue #2064: Cargo is overeager to pull in multiple copies of a crate
Issues needing a decision
- Issue #29815: Warn must_use in tuple
- Issue #30780: enable rust pretty printers when debugging with cgdb
RFC phase
- FCP PR #1317: Rust Language Server (IDE support)
- PR #1133: Make Cargo aware of standard library dependencies
- PR #1296:
RFC: Add an
aliasattribute to #[link] and -l - PR #1459: Add a used attribute
- Issue #635: Use benchmarks to set up a website tracking rust performance
- Issue #648: separate rust-format or rustfmt tool that does the pretty-printing
- Issue #816: Custom test frameworks
- Issue #1061: Rust, Windows, and MSVC