AaronBallman wrote: > @AaronBallman Do you happen to know if there’s precedent for this?
We recently started [documenting our guarantees](https://clang.llvm.org/docs/LibClang.html#abi-and-api-stability), and I think this falls under "Removing an explicitly deprecated API after a suitably long deprecation period." So I think the right path forward is to add stub APIs which fail gracefully, mark the APIs as deprecated and explain that the underlying functionality has been removed so these APIs only exist for ABI compatibility, and then we can remove them in a few years. Do others think that's a reasonable plan? https://github.com/llvm/llvm-project/pull/119269 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
