Here at the start we have only a handful of RFCs, but there is quite a lot of pending work and future projects to get the ball rolling on throughout the rfcs, rust, cargo, and crates.io repos. To highlight a few prominent issues that may have quite a large impact:
- rust-lang/cargo#482 Specifying a custom output directory for Cargo
- rust-lang/cargo#1007 Making platform-specific dependencies much more ergonomic and robust.
- rust-lang/rfcs#1061 Filling in the next set of cracks in Rust's MSVC support.
This is by no means an exhaustive list, so be sure to check out many of the P-high issues below for more upcoming projects!
- 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
- PR #595: Output option handling
- PR #1133: Make Cargo aware of libstd dependencies
- Issue #19286: Move automation off mac minis, onto macstadium
- Issue #23757: Add beta/stable integration testing
- Cargo Issue #482:
Sharing
targetdirectories - 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 #1215:
cargo buildsometimes causes overrides to be built when it is already built - Cargo Issue #1251: Build dependency awareness
- Cargo Issue #1600: cargo always rebuilds crates, even if source is unchanged