Rain
It would be very convenient to support allocating `OsStr` and `Path` instances in a `Bump`. Unfortunately the underlying byte representation isn't exposed on Windows, so we'll probably have to return...
Hi there! shellharden looks fantastic, and I was considering integrating it into some lint infrastructure we have. However, it looks like the only stable interface is a binary. Would you...
This commit stack makes criterion compatible with nextest using the rules [listed here](https://nexte.st/book/custom-test-harnesses.html). Each commit is independently reviewable. Note that none of these changes do anything special for nextest --...
Hey :) So `serde_json`'s serializer and deserializer support `Write` and `Read` respectively, but unfortunately they aren't compatible with tokio. The basic rule of I/O with `tokio` (I should contribute some...
`cargo hakari` 0.9.9 used a scheme where it would assume everything could target the same [workspace-hack crate](https://crates.io/crates/workspace-hack). Unfortunately, it turns out that cargo has a few bugs which prevent that...
still working on this as we go through guppy's architecture.
`toml_edit` looks like the future of toml parsing and serialization in Rust: its design avoids `ValueAfterTable` issues, provides greater control over formatting if necessary, etc. I think it makes sense...
Still TODO: * [ ] Get `cargo-compare` running on Windows. Some of the failures we're seeing are: ``` thread 'tests::workspace_tests::cargo_guppy::proptest_compare' panicked at 'compute_diff succeeded: failed to read `\\?\D:\a\cargo-guppy\cargo-guppy\internal-tools/benchmarks\Cargo.toml` Caused by:...
`guppy` seems to really consist of two separate layers: 1. The core graph handling, which is based on top of petgraph and is independent of any Rust-specific details. This consists...
Cargo uses a version strategy that can be described as "maximal": by default, Cargo picks the highest version that satisfies the provided constraints. I believe that this is generally the...