basically, if you plan to evolve your software in observable ways, you do have to decide *some* things that may "break" users are actually not breaking changes, because ultimately all observable behavior can potentially be depended upon (hyrum's law!)
once you accept that, then it becomes a matter of degrees. the right answer is different for different bits of software, e.g. clippy has a far more lax stability policy than rustc, because it is fundamentally a developer tool
Comments