Re: [swift-dev] COFF indirect addressing and protocol conformance tables ABI issues

On Tue, Jul 5, 2016 at 6:28 PM, John McCall wrote: > On Jul 5, 2016, at 5:56 PM, Saleem Abdulrasool > wrote: > On Tue, Jul 5, 2016 at 10:30 AM, John McCall wrote: > >> > On Jul 3, 2016, at 2:40 PM, Saleem Abdulrasool >> wrote: >> > Hello again, >> > >> > I come bearing more problems :-). >> >

Re: [swift-dev] Fixit for trailing closures

> On Jul 5, 2016, at 7:57 PM, Erica Sadun via swift-dev > wrote: > > > >> On Jul 5, 2016, at 7:42 PM, Xi Ge via swift-dev > > wrote: >> >>> >>> On Jul 5, 2016, at 5:39 PM, Xi Ge via swift-dev >> > wrote: >>> On Jul 5, 2016, at 5:

Re: [swift-dev] Fixit for trailing closures

> On Jul 5, 2016, at 21:29, Xi Ge wrote: > >> >> On Jul 5, 2016, at 8:31 PM, Jordan Rose > > wrote: >> >>> >>> On Jul 5, 2016, at 17:19, Ben Langmuir via swift-dev >> > wrote: >>> On Jul 5, 2016, at 4:34 PM, Xi Ge via swift

Re: [swift-dev] COFF indirect addressing and protocol conformance tables ABI issues

> On Jul 6, 2016, at 7:33 AM, Saleem Abdulrasool wrote: > On Tue, Jul 5, 2016 at 6:28 PM, John McCall > wrote: >> On Jul 5, 2016, at 5:56 PM, Saleem Abdulrasool > > wrote: >> On Tue, Jul 5, 2016 at 10:30 AM, John McCall >

Re: [swift-dev] CI outage for SDK and source updates, and branching for Preview 3

Reminder: Starting update right now. During this update, please don’t trigger pull request testing on GitHub. Thanks, Mishal Shah > On Jul 5, 2016, at 12:55 PM, Nicole Jacque via swift-dev > wrote: > > Hello All- > > Tomorrow we will be bringing down the CI temporarily starting around 10

Re: [swift-dev] Fixit for trailing closures

> On Jul 6, 2016, at 9:39 AM, Jordan Rose wrote: > >> >> On Jul 5, 2016, at 21:29, Xi Ge mailto:xi...@apple.com>> >> wrote: >> >>> >>> On Jul 5, 2016, at 8:31 PM, Jordan Rose >> > wrote: >>> On Jul 5, 2016, at 17:19, Ben Langmuir via swift-dev >>>

Re: [swift-dev] Handling Windows C library Matrix

For anyone watching this thread, Saleem broke it down a little further for me in https://github.com/apple/swift/pull/3326. For now we decided to just add an autolink flag to the frontend (not the driver) to make sure we don't get the "wrong" C library by accident. We'll need to discuss further h

Re: [swift-dev] Fixit for trailing closures

> On Jul 6, 2016, at 10:31, Xi Ge wrote: > > > > > >> On Jul 6, 2016, at 9:39 AM, Jordan Rose > > wrote: >> >>> >>> On Jul 5, 2016, at 21:29, Xi Ge mailto:xi...@apple.com>> >>> wrote: >>> On Jul 5, 2016, at 8:31 PM, Jordan Rose >>>

Re: [swift-dev] Descriptive Protocol non-conformance errors

> On Jun 25, 2016, at 1:19 PM, Sean Alling via swift-dev > wrote: > > Hi everyone, > > I’m suggesting a change to the compiler that returns an error when an object > 'does not conform to protocol’ to nest sub-errors that’ll list what > properties and methods the object hasn’t implemented. >

Re: [swift-dev] Descriptive Protocol non-conformance errors

> On Jul 6, 2016, at 8:24 PM, Douglas Gregor via swift-dev > wrote: > > >> On Jun 25, 2016, at 1:19 PM, Sean Alling via swift-dev >> wrote: >> >> Hi everyone, >> >> I’m suggesting a change to the compiler that returns an error when an object >> 'does not conform to protocol’ to nest sub-e

Re: [swift-dev] Descriptive Protocol non-conformance errors

I have wanted this for a long time. (In fact I believe I filed a radar some time ago for this!) Filling in the interface stubs saves so much time! Michael > On Jul 6, 2016, at 8:40 PM, Xi Ge via swift-dev wrote: > >> >> On Jul 6, 2016, at 8:24 PM, Douglas Gregor via swift-dev >> wrote: >>