Re: [swift-dev] Feature Proposal to improve Mixed Frameworks support

Ah, great, that's even better. My solution is overkill compared to this and I think you're covering all the interesting cases anyway. I would love to work on the implementation if it's not assigned to anyone internally yet. (I've seen you mentioned there's a radar already?) Cheers. -- Slds, Gon

Re: [swift-dev] Feature Proposal to improve Mixed Frameworks support

> On Jun 29, 2017, at 4:39 PM, Jordan Rose wrote: > > >> On Jun 29, 2017, at 16:35, Daniel Dunbar > > wrote: >> >> >>> On Jun 29, 2017, at 10:43 AM, Jordan Rose via swift-dev >>> mailto:swift-dev@swift.org>> wrote: >>> >>> Thanks for following through on this

Re: [swift-dev] Feature Proposal to improve Mixed Frameworks support

> On Jun 29, 2017, at 16:35, Daniel Dunbar wrote: > > >> On Jun 29, 2017, at 10:43 AM, Jordan Rose via swift-dev > > wrote: >> >> Thanks for following through on this, Gonzalo! (The two of us talked about >> this briefly at WWDC.) My idea was a little less clever t

Re: [swift-dev] Feature Proposal to improve Mixed Frameworks support

> On Jun 29, 2017, at 10:43 AM, Jordan Rose via swift-dev > wrote: > > Thanks for following through on this, Gonzalo! (The two of us talked about > this briefly at WWDC.) My idea was a little less clever than yours: just > always include the internal members in the main header unless you prov

Re: [swift-dev] Feature Proposal to improve Mixed Frameworks support

Thanks for following through on this, Gonzalo! (The two of us talked about this briefly at WWDC.) My idea was a little less clever than yours: just always include the internal members in the main header unless you provide the name of a second header to put them in. (I called this flag -emit-obj