Issue was: new type inference caused problems for old version of the time crate. Newer versions worked with 1.80, but many crates weren't updated to the latest.
> Also, the blobiness was never going to be a part of the public facing API - is it really the hypothetical serde’s fault NixOS breaks?
According to Semver - no. According to people affected - yes.
I often state this, but:
Backwards compatibility ⇒ Semver (read: Backwards compatibility implies SemVer, but not the other way around).
Who's right? Is it fine to speed up compilation but disrupt people using serde on Arch? It depends. According to strict Backwards compatibility guarantee - no. However according to them, you need to backport bugs and exploits.
No, that's a separate issue in 1.80. See https://internals.rust-lang.org/t/type-inference-breakage-in...
Issue was: new type inference caused problems for old version of the time crate. Newer versions worked with 1.80, but many crates weren't updated to the latest.
> Also, the blobiness was never going to be a part of the public facing API - is it really the hypothetical serde’s fault NixOS breaks?
According to Semver - no. According to people affected - yes.
I often state this, but:
Backwards compatibility ⇒ Semver (read: Backwards compatibility implies SemVer, but not the other way around).
Who's right? Is it fine to speed up compilation but disrupt people using serde on Arch? It depends. According to strict Backwards compatibility guarantee - no. However according to them, you need to backport bugs and exploits.