[Lldb-commits] [PATCH] D134878: Update developer policy on potentially breaking changes

[Aaron Ballman via Phabricator via lldb-commits]

aaron.ballman added a comment.

In D134878#3869947 <https://reviews.llvm.org/D134878#3869947>, @mehdi_amini wrote:

> From what I saw when you posted the discourse thread initially, I understand you're targeting user-visible features, and mostly from the "toolchain" side of the project.
> However I find the language here to be potentially confusing for the API surface of the libraries: that is how much of this applies to the LLVM C++ libraries API surface?
> If this is out-of-scope, can this be called out more explicitly?

Sure! Would it help to add a paragraph before the bulleted list in `breaking` that says something along the lines of:

The C++ interfaces of individual library components of projects like LLVM or Clang are not intended to be stable interfaces. Potentially disruptive changes to such C++ interfaces do not constitute a breaking change unless the disruption is exposed via another mechanism such as a stable C API.

(Feel free to wordsmith it!)


Repository:
  rG LLVM Github Monorepo

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D134878/new/

https://reviews.llvm.org/D134878