[cfe-dev] Is ModuleBuilder useful to anyone?

[Mark Boyall]

I have a hard dependency on it and have no idea how I could handle losing that API

-----Original Message-----
From: "Keno Fischer" <kfischer at college.harvard.edu>
Sent: ‎30/‎12/‎2014 07:32
To: "Yaron Keren" <yaron.keren at gmail.com>; "vvasilev at cern.ch" <vvasilev at cern.ch>
Cc: "cfe-dev at cs.uiuc.edu Developers" <cfe-dev at cs.uiuc.edu>; "Rafael Ávila de Espíndola" <rafael.espindola at gmail.com>; "Reid Kleckner" <rnk at google.com>; "Chandler Carruth" <chandlerc at google.com>; "Richard Smith" <richard at metafoo.co.uk>; "Mark Boyall" <wolfeinstein at gmail.com>; "chisophugis at gmail.com" <chisophugis at gmail.com>
Subject: Re: Is ModuleBuilder useful to anyone?

Personally I'm not using it, but I recall that cling might be?


On Tue, Dec 30, 2014 at 8:22 AM, Yaron Keren <yaron.keren at gmail.com> wrote:

Following


 http://lists.cs.uiuc.edu/pipermail/cfe-commits/Week-of-Mon-20140825/113355.html



In tree,  ModuleBuilder has one user (+test) only, the BackendConsumer.
The interaction between the two classes complicates BackendConsumer logic. For instance, both hold the same Module * in two different std::unique_ptr and dance around this problem to avoid releasing it twice or none. 



Out of tree, is ModuleBuilder limited functionality useful to any project?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20141230/9c500c81/attachment.html>