Rain
Thanks! Can this use a very simple version check, similar to: https://github.com/camino-rs/camino/blob/467b33692ac2224f6ccfb6b4e96d7dfe2ea09ec7/build.rs#L32-L34 I don't think it's necessary to pull down a dependency here.
> Side note: trying to run tests with cargo run -p cargo-nextest -- nextest run --all-features failed with tracing complaining that it failed to set a global subscriber since one...
Released this as part of cargo-nextest 0.9.82. Thanks again! > Ah good catch, I'll try and fix this. Fixed in https://github.com/nextest-rs/nextest/commit/11623d5ce06fd63ff3803499e594400876bac502.
Thanks for the PR! I'm currently quite sick but will look when I'm better.
Thanks @ArhanChaudhary -- would you be willing to submit a PR even with your WIP? Happy to have a look.
FYI this will need to be to libc 0.2.161 to pull in the fix for https://github.com/rust-lang/libc/pull/3983.
I made this change in https://github.com/rust-lang/rust/pull/131851 as well since I needed it too. Happy to rebase if this lands first.
Basically, if there's ever a serde v2 or a proptest v2, then we don't want to release a camino v2 was my thought.
I think producing an error might break existing users (I wish I had the foresight to do this at the time I was releasing v1.0), and I don't think Cargo...
See https://github.com/camino-rs/camino/commit/4ae167f76e5c6f846a0bf3ec8687c8e270882117 -- the build script now emits warnings. This won't produce warnings by default, but will with `cargo build -vv` (which some folks run in CI at least). Again,...