Semver violations are common, better tooling is the answer - eviltoast
  • notriddle@programming.dev
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    That’s a good point.

    cargo-semver-check should definitely provide a way to mark syntactically-public items as “de-facto private,” because some projects just need to do bad things and leaving them out in the cold is not helpful. But you’ve convinced me that doc(hidden) is a poor way to do it.