Subteam report: tools 2015-12-04
Highlights
With Thanksgiving last week and the 1.5 release just around the corner this was a quiet few weeks for the tools team, but that doesn't mean exciting things weren't happening!
- @brson's been working on getting a port of Rust to work with Emscripten, and initial results are promising with "hello world" already working!
- Support has landed in Cargo to allow build scripts to explicitly specify their file dependencies. This should reduce the number of rebuilds seen because Cargo reruns a build script.
- The libc crate now tests against rumprun, becoming the first BSD platform to have automation verifying the definitions in libc.
- The deadline for returning a hard error from publishing crates with a wildcard version has been pushed back as the Cargo warning will be released with 1.5.
Dashboard
High priority issues
- Issue #19286: Move automation off mac minis, onto macstadium
- 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
RFC phase
- FCP PR #1296:
RFC: Add an
aliasattribute to #[link] and -l - PR #1133: Make Cargo aware of standard library dependencies
- PR #1246: Compiler UX Guidelines RFC
- PR #1284: Machine-readable output of tests
- PR #1317: Changes to the compiler to support IDEs
- PR #1361: RFC: Improve Cargo target-specific dependencies
- 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