Unlike the way some languages' package systems work, Rust crates don't cleanly separate the public interface from the private implementation. In practice a cra

Unlike the way some languages' package systems work, Rust crates don't cleanly separate the public interface from the private implementation. In practice a crate's public interface is effectively scattered throughout a number of modules. There's no separate textual interface definition that you could diff to see what you changed without also seeing changes to the implementation. Clients importing your library compile against the whole source. So in practice if you want to check whether you changed your public interface unintentionally, your best bet is to compare the old and new output of Rust's automated documentation system, which by default is describing only the public interface. Cargo-semver-checks attempts to automate that.