On Mon, Aug 25, 2014 at 7:26 PM, Sean Silva <[email protected]> wrote:
> as we get compelling use cases, we bring up the necessary headers into > include/ to satisfy them, making any necessary incremental changes to > better serve the use case. Yes, but that's exactly what we're lacking here: a compelling use case that outlines what API it actually needs in the public headers.
_______________________________________________ cfe-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
