Subteam report: tools 2016-05-08
Highlights
A relatively quiet few weeks with regards to tooling and infrastructure, but some of the highlights were:
- A new approach has landed in the compiler and feedback would be most welcome!
- The
target_envvalue for many Linux ARM targets has been normalized to just "gnu". - Nightlies for i686 FreeBSD Cargo are now available.
- A new
--forceflag forcargo installis now available to overwrite existing binaries. - The RFC for Cargo workspaces has been accepted.
Dashboard
High priority issues
- Issue #32445: Regression on nightly: doctest on recursion_limit crashes rustdoc
- Cargo Issue #782: Resolve errors are likely quite obscure
- Cargo Issue #1251: Build dependency awareness
- Cargo Issue #2064: Cargo is overeager to pull in multiple copies of a crate
Issues needing a decision
RFC phase
- 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
- PR #1489: Extended static linking
- PR #1509: Add space-friendly arguments
- PR #1567: Normalization for long error codes explanations RFC
- PR #1573: Supporting code generators with source maps and multiple source directories
- PR #1608:
clarify 'root' with 'root crate' or 'root
Cargo.toml' - 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
Implementation phase
- Issue #33132: Tracking issue for adding a new cdylib crate type
- Issue #33134: Tracking issue for -C overflow-checks
Stabilization phase
- Issue #31847: Tracking issue for accepting unstable flags in stable compilers
- Issue #33261: Tracking issue for JSON errors