aaron.ballman added a comment. In D151607#4383132 <https://reviews.llvm.org/D151607#4383132>, @kazu wrote:
> In D151607#4380757 <https://reviews.llvm.org/D151607#4380757>, @erichkeane > wrote: > >> Since this is part of the public API, do we need to publish/alert folks of >> this? This could perhaps be in use by someone using libclang/etc, right? > > I don't think we guarantee the API stability. For the *C* API, this is > clearly documented: > > https://llvm.org/docs/DeveloperPolicy.html#c-api-changes > > There has been an effort to document something similar about the C++ API: > > https://lists.llvm.org/pipermail/llvm-dev/2020-July/143613.html > > but I don't know exactly what happened to it. We try to keep the C API as stable as we can, but the C++ API is fair game to change as we need to. If someone runs into an issue where they need this functionality, they can let us know what their needs are and we can evaluate from there. Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D151607/new/ https://reviews.llvm.org/D151607 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
