> On Sep 13, 2016, at 8:16 PM, Michael Ilseman via swift-users
> wrote:
>
>
>> On Sep 13, 2016, at 8:14 PM, Rick Mann wrote:
>>
>> But the Apple declaration (accessible via Xcode) of the method it's based on
>> looks like this:
>>
>> open func enumerator(at url: URL,
>> includingProperti
> On Sep 13, 2016, at 8:37 PM, Shawn Erickson wrote:
>
> I am in the process of updating to Xcode 8 release so I can't confirm at the
> moment but I am fairly sure I hit a situation with being asked to implement a
> func from a protocol that got autocompleted with @escape nested as shown. It
> On Sep 14, 2016, at 7:50 AM, Patrice Kouame via swift-users
> wrote:
>
> 1. File those bugs and issues in radar, but lower your expectations a bit.
> That’s how I usually vent my frustrations. Just imagine the thousands they
> have to sift through...
> 2. Be constructive: if possible prov
All - you have the privilege of watching the sausage being made. That took
courage and much foresight from some great Apple engineers that grace these
threads.
1. File those bugs and issues in radar, but lower your expectations a bit.
That’s how I usually vent my frustrations. Just imagine t
The Art of Diplomacy…
Keep doing the great work, lot of us have to much work in our job and/or not
the skills (my case) to help you in this so interesting journey.
Thanx
Gerard
> On 14 Sep 2016, at 05:56, Chris Lattner via swift-users
> mailto:swift-users@swift.org>> wrote:
>
> On Sep 13, 20
