On Sun, Feb 1, 2026, at 1:32 AM, Peter Michael Green wrote: >> Please upgrade crate bytesize to v2. On the one hand, it looks like there >> were some fairly significant changes. > >> • Add support for `no_std` targets. >> • Use IEC (binary) format by default with `Display`. >> • Use "kB" for SI unit. >> • Add `Display` type for customizing printed format. >> • Add `ByteSize::display()` method. >> • Implement `Sub<ByteSize>` for `ByteSize`. >> • Implement `Sub<impl Into<u64>>` for `ByteSize`. >> • Implement `SubAssign<ByteSize>` for `ByteSize`. >> • Implement `SubAssign<impl Into<u64>>` for `ByteSize`. >> • Reject parsing non-unit characters after whitespace. >> • Remove `ByteSize::to_string_as()` method. >> • Remove top-level `to_string()` method. >> • Remove top-level `B` constant. > On the other hand, I think this is mostly intended for UI > stuff where precise behaviour is not so critical. > > Preliminary analysis of rdeps > > prs - upstream moved to v2 with no significant code changes > python-cramjam - rc buggy and not in testing > rust-bat - use of bytesize seems quite minimal and tests pass with the > new version. > rust-cargo - upstream has moved away from bytesize, there is an issue > filed on salsa about updating cargo. > rust-gix-features - upstream bumped dependency in version 0.42 without > making any code changes. > rust-kmon - upstream has updated, but hasn't made a release yet. > rust-prodash - upstream updated with minimal code changes. > rust-systemstat - use of bytesize seems fairly intensive, still on 1.x > upstream > rust-wasmtime - still on 1.x upstream, currently build-dependency only. > > My gut feeling is we should probably do this after the gix/cargo update.
I hope to rebased and finally pull the trigger on that this week after FOSDEM..
