================ @@ -373,19 +373,21 @@ implementation of the facilities by Clang may change behavior as bugs are fixed, features get implemented, etc. The library should be ABI and API stable over time, but ABI- and API-breaking -changes can happen in the following situations: +changes can happen in the following (non-exhaustive) situations: * Adding new enumerator to an enumeration (can be ABI-breaking in C++). * Removing an explicitly deprecated API after a suitably long deprecation period. -* Uses of implementation details, such names or comments that say something is - "private", "reserved", "internal", etc. +* Using implementation details, such as names or comments that say something + is "private", "reserved", "internal", etc. +* Bug fixes or changes to Clang's internal implementation, or (rarely), bug ---------------- AaronBallman wrote:
I think bug fixes to Clang internals are always fair game for us and something libclang folks will have to react to, which is why it's important to disallow multiple versions of the library from interacting. But fixes to libclang itself is something I think we can be more judicious about. e.g., adding a forgotten enumerator really shouldn't be a problem. Renaming one we don't like the name for is more disruptive and something we'd likely avoid doing. https://github.com/llvm/llvm-project/pull/141657 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
