Rust is looking to seal std::os::unix::fs::MetadataExt:
rust-lang/rust#118916
As in #271 (which was before cap-std 1.0), cap-std can switch to defining its own copies of these traits. And since cap-std seems to be the only crate in the ecosystem that is affected, it should probably do this, to unblock std evolution.
However, this is a semver-incompatible change, so it'll require bumping cap-std to 3.0.
@cgwalters, who I know is particularly impacted by semver bumps
Rust is looking to seal
std::os::unix::fs::MetadataExt:rust-lang/rust#118916
As in #271 (which was before cap-std 1.0), cap-std can switch to defining its own copies of these traits. And since cap-std seems to be the only crate in the ecosystem that is affected, it should probably do this, to unblock std evolution.
However, this is a semver-incompatible change, so it'll require bumping cap-std to 3.0.
@cgwalters, who I know is particularly impacted by semver bumps