Gregory's Server@jsbarretto if your private methods leak into public traits, you're doing it wrong; you should be using sealed supertraits. However, I do like the idea of having `doc(hidden)` stuff be implementation details that you shouldn't have to use but are kinda allowed to; thus being semi-private interfaces that aren't subject to semver.
|
3 comments
 @jsbarretto I think I've found the definitive answer to your answer. It turns out `doc(hidden)` is not part of the public API, and as such, is considered private in terms of semver. https://rust-lang.github.io/api-guidelines/future-proofing.html  @Alonely0 The phrase 'not allowed for user to call' is, IMO, not an explicit enough guarantee here, and it seems there's at least a little divergence of opinion in the community over this. |
@Alonely0 I'm already using sealed supertraits. Problem is, they make impls much harder to observe in the docs and result in substantially worse error messages.