Subteam report: tools 2016-05-20
Highlights
- An excellent blog post about rustup was published, detailing the vision for the tool and next steps.
- Custom panic runtimes are now implemented which means that the
compiler flag
-C panic=abortcan now be use to implement panics as aborts. - The new rust build system can now run crate tests which should bring it up to feature parity for tier 1 platforms.
- Various Android targets have [seen][android1] [updates][android2] to enable more features and align them with the upstream definitions.
- A new crate type,
cdylib, is now available for production by the compiler which is optimized for producing a dynamic library with a C API. More information can be found in the relevant RFC. - Cargo will now retry failed network requests by default if they look like they're spurious failures.
- Cargo will now emit status to stderr instead of stdout.
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
- FCP PR #1567: Normalization for long error codes explanations RFC
- 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 #1573: Supporting code generators with source maps and multiple source directories
- PR #1615: Let Cargo put data into platform-specific directories
- 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 #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