tools and infrastructure
About the cargo category
[Pre-RFC] Cargo Safety Rails
How about changing [lib] to [[lib]], to allow multiple library in a crate?
How does cargo handle files?
Cargo::util::config::* - why all the Cells?
Cargo package aliases
Handling compilation failures in integration tests
Coverage out of the box?
[Pre-RFC] Development Build Scripts
[Pre-RFC] Cargo Templates
Maybe pre-RFC: improving "-"/"_" in cargo/crates.io
[Pre-RFC] Provide flavors for libraries (non-additive features)
SemVer Compatibility Tool - GSoC Proposal Draft and Discussion
Building with minimum version of dependencies
Proposal: make cargo output dep-info
No_std = true metadata in Cargo.toml
Default opt-level for release builds
Cargo support for build-script filters, lints, and link-path providers
Direct support for pkg-config in Cargo
Is a shared build cache a good fit for Cargo?
Differentiating author vs. maintainer roles in Cargo.toml
[pre-RFC] Security advisories as part of crates.io metadata
Crates.io Discoverability and Engagement: starting the conversation
Idea: Cargo git dependency commit pinning flag
Dependency mediation in cargo
Should "cargo new" default to applications?
Programmatic Access/Use of Cargo
Cargo Compatibility Guarantees?
Cargo is gaining the ability to retry network failures
next page →