A patch to move codegen includes into public include

[Sean Silva]

On Mon, Aug 25, 2014 at 5:30 PM, Chandler Carruth <chandlerc at google.com>
wrote:

>
> On Mon, Aug 25, 2014 at 5:18 PM, Sean Silva <chisophugis at gmail.com> wrote:
>
>> Does any part of LLVM actually *design* a public API (besides the C
>> stuff), rather than having the public API be just the one used by clients
>> within LLVM? Actually, I feel like there would be pushback for trying to do
>> that.
>
>
> Is this a serious question?
>

Yes. It was in reply to a statement that seemed to suggest a "design public
API up front, then implement the whole thing" approach (not a
"incrementally approach our use cases, carefully considering the design of
the API at each step" approach). It seems like the "design API up front"
approach is the exception rather than the norm in LLVM-land, so it was
strange to see it being suggested as a preference.

-- Sean Silva


>
> We very carefully consider changes to the IR's public APIs. Same for the
> pass management and other APIs.
>
> The Clang ASTs have a *huge* number of external users of their API and API
> changes are considered carefully.
>
> The Edit, Tooling, Rewrite, and Format libraries all have public APIs that
> did go through a reasonable amount of design.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-commits/attachments/20140825/a4767448/attachment.html>