Ed Page
Ed Page
### What it does Lint when a dependency version requirement is lower than the resolved dependencies version. ### Advantage - Low effort way of ensuring version requirements are not too...
### What it does Checks for negative feature names with prefix `no-` or `not-` See also https://rust-lang.github.io/rust-clippy/master/index.html?groups=cargo#negative_feature_names ### Advantage Features are supposed to be additive, and negatively-named features violate it....
### What it does Checks for feature names with prefix `use-`, `with-` or suffix `-support` See also https://rust-lang.github.io/rust-clippy/master/index.html?groups=cargo#/redundant_feature_names?groups=cargo ### Advantage These prefixes and suffixes have no significant meaning. ### Drawbacks...
### What it does Warns if a version req is `1.3` or `1` rather than `1.3.5` ### Advantage This can help with more correct minimum bounds because patch packages can...
### Summary RFC: [#2523](https://github.com/rust-lang/rfcs/pull/2523) Original issue: N/A Implementation: - [ ] Initial implementation Documentation: https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#cfg-version Allow dependencies conditioned on the Rust version in a way that matches with `#[cfg(version)]` ```toml...
The Cargo team has started a Call for Testing for `build-dir` which allows users to move intermediate artifacts out of their `target-dir`. This may break affect the behavior of `cargo...
Cargo normalizes `CARGO_FEATURE_*` feature names, making it so there isn't an exact 1:1 between the env variable and `Cargo.toml` (see rust-lang/cargo#3702). As of Cargo 1.85, Cargo now provides `CARGO_CFG_FEATURE`, see...
My personal goal is first-class custom test harnesses with a de facto harness that offers the flexibility of pytest which would make it so I no longer need libtest-mimic (unsure...
To reproduce, I had to do: ```console $ CARGO_RESOLVER_INCOMPATIBLE_RUST_VERSIONS=fallback cargo +nightly generate-lockfile $ cargo +1.65 check error[E0277]: `Sender` cannot be shared between threads safely --> src/lib.rs:521:29 | 521 | scope.spawn(||...
I can see this being debatable for regular methods. - The name could be viewed as documentation - Name changes could imply a change in semantic meaning However, where this...