[PATCH] D12685: Document the stability policy for LLVM-C APIs.

[Amaury SECHET via llvm-commits]

deadalnix added a comment.

@echristo the C APi test is not intended as to freeze the API, but as to make sure that things are done intentionally. It follow the recent landingpad change fiasco.

If a change is made that break the C API, then the test is going to break. Either this breakage is intentional, in which case the test can be updated to reflect the change, or the breakage is not intentional and can be fixed.

The test is intended to cover read and write IR, which seems like a minimum to have for the API to be useful.

Generally, I think the best effort policy proposed here is the right balance. Freezing the C API would impair refactoring capabilities, while changing it in the same way it is done with the C++ API would cause hard to debug problems when using LLVM from other languages.


http://reviews.llvm.org/D12685