Of course! `cargo-semver-checks` is not a replacement for testing. It's exactly the kind of tool you describe:
> Knowing that something is _definitely_ a breaking change because an API was removed or modified in an incompatible way will still save you time.
We want to help maintainers spot accidental breaking changes early — before they are released — instead of both maintainers and downstream projects having to scramble for fixes after an accidental breaking change is released.
> Knowing that something is _definitely_ a breaking change because an API was removed or modified in an incompatible way will still save you time.
We want to help maintainers spot accidental breaking changes early — before they are released — instead of both maintainers and downstream projects having to scramble for fixes after an accidental breaking change is released.