[llvm-dev] [LLVMdev] [RFC] Developer Policy for LLVM C API
Eric Christopher via llvm-dev
llvm-dev at lists.llvm.org
Sun Aug 16 21:51:34 PDT 2015
On Sun, Aug 16, 2015 at 9:49 PM deadal nix <deadalnix at gmail.com> wrote:
> 2015-08-16 21:47 GMT-07:00 Eric Christopher <echristo at gmail.com>:
>> On Sun, Aug 16, 2015 at 6:45 PM deadal nix via llvm-dev <
>> llvm-dev at lists.llvm.org> wrote:
>>> Chiming in with http://reviews.llvm.org/D10725
>>> Being able to read and generate IR is at least some very basic thing we
>>> can agree on is needed. Can we get some testing for it ? Personally I don't
>>> really mind if this is going to be stable or not, but at least, having some
>>> test coverage would allow to take whatever path that is going to be taken
>> Right, and that's the problem. Expanding the C API to cover reading and
>> generating IR in a stable way will lock the C++ API down in a way that I'm
>> not comfortable with - I think it has already gone too far.
> That seems like a bare minimum.
> The C++ evolve from one version to another, what is preventing the C API
> to do the same ?
The promise of stability. We don't promise that the C++ API will stay
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the llvm-dev