cargo
cargo copied to clipboard
rust-lang
The Rust package manager
This extends the `#[cargo_test]` attribute to support some additional requirements to control whether or not a test can run. The motivation for this is: * Can more clearly see when...
This PR addresses issues raised in rust-lang/cargo#9525. Specifically: 1. It enables examples to be scraped from `#[test]` functions, by passing additional flags to Rustdoc to ensure that these functions aren't...
Fixes #9217. Continuation of https://github.com/rust-lang/cargo/pull/9221.
**Problem** Even with `TERM=dumb`, cargo buffers ~~stderr~~ stdout, meaning I do not see things printed to stdout without a trailing `\n`. For Miri, we use `cargo rustc` set up RUSTC_WRAPPER...
### Problem With the rustup changes to set `$RUSTC` et al, it's become more likely that people will accidentally use `+toolchain` on cargo/rustc/etc directly rather than through the rustup shims....
**Describe the problem you are trying to solve** For enterprise integration, it is desirable to control which version of cargo is being run and with what environment. This can be...
If the workspace and package specify or default to different resolver versions then this will cause inconsistencies in build behavior between a development build within the workspace and the published...
### Problem Because the resolver is a global setting in workspaces, and workspaces don't have edition settings, I believe that it is very easy to accidentally use the old resolver...
### Problem I'm writing a proc macro that generates code based on the operating system for which the library/executable is being compiled. This macro generates OS specific code for windows/linux/macos/android....
Recent versions of Windows have removed the limitation on filenames like `aux` or `con`. This change allows the `package::reserved_windows_name` to still pass by first trying to create a file with...
