The API semver RFC did not take into account the impact of "OIBIT" traits (which have a .. impl). In particular, these traits can introduce downstream sensitivity to every aspect of a data type's representation, even if that representation is private.
Effectively, OIBITs make it possible for downstream crates to make promises on behalf of upstream crates that can easily be broken.
I don't think this should change anything about the policy itself, but it'd be worth amending the RFC to discuss it.
The API semver RFC did not take into account the impact of "OIBIT" traits (which have a
..impl). In particular, these traits can introduce downstream sensitivity to every aspect of a data type's representation, even if that representation is private.Effectively, OIBITs make it possible for downstream crates to make promises on behalf of upstream crates that can easily be broken.
I don't think this should change anything about the policy itself, but it'd be worth amending the RFC to discuss it.