Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
To 1.72 rustup update stable rustc --version # rustc 1.72.0 (5680fa18f 2023-08-23) cargo fix --allow-dirty # tells me to set resolver vim Cargo.toml # set the resolver cargo build cargo test # see snapshot failure UPDATE_SNAPSHOTS=1 cargo test # update snapshot cargo test # confirm snapshot failure is gone Context for the resolver warning: warning: some crates are on edition 2021 which defaults to `resolver = "2"`, but virtual workspaces default to `resolver = "1"` note: to keep the current resolver, specify `workspace.resolver = "1"` in the workspace root's manifest note: to use the edition 2021 resolver, specify `workspace.resolver = "2"` in the workspace root's manifest Context for the snapshot failure: ... I sure wish I could find the changelog entry or an issue or a commit explaining why `std::fmt` (via `format!("{:#?}", ...)`) started outputting "\0" as "\0" instead of "\u{0}", but I can't find it... - https://releases.rs/ - https://doc.rust-lang.org/std/fmt/ - https://github.com/search?q=repo%3Arust-lang%2Frust+str%3A%3Afmt&type=issues ... no wait for it, wait for it! Here it is: - rust-lang/rust@2ac9efb - https://github.com/rust-lang/rust/releases/tag/1.61.0 (first appeared in this version, but not mentioned in changelog) - rust-lang/rust#95345
- Loading branch information