More of a swift-dev topic. CC'ing there, BCC'ing evolution.
Thanks!
I’ll track the issue over there.
I do have to note that this is a very strange of writing Nat. Why recurse
through a protocol type instead of recursing concretely?
My examples are extracted from a more complex codebase that r
Hi everyone,
I failed to find the reason why Swift does not allows a non-escaping parameter
to be assigned to a local variable. Here is a minimal example:
func f(_ closure: () -> Int) {
let a = closure
}
I do understand that assigning a non-escaping closure to a variable whose
lifetime exc
assignments
would have to be disallowed.
Best,
Dimitri
On 31 May 2017, at 22:10, John McCall
mailto:rjmcc...@apple.com>> wrote:
On May 31, 2017, at 12:21 PM, Dimitri Racordon via swift-dev
mailto:swift-dev@swift.org>> wrote:
Hi everyone,
I failed to find the reason why Swift does not
cc...@apple.com>> wrote:
On May 31, 2017, at 12:21 PM, Dimitri Racordon via swift-dev
mailto:swift-dev@swift.org>> wrote:
Hi everyone,
I failed to find the reason why Swift does not allows a non-escaping parameter
to be assigned to a local variable. Here is a minimal example:
func f(_ cl
Hello fellow Swift enthusiasts.
I’m struggling to understand why type inference fails to solve Collection s
associated types while trying to provide it with a default implementation, via
protocol extensions, when an additional subscript is provided. Here is a
minimal example:
protocol SearchTr
I’d be more than happy to help as well!
> On Nov 16, 2017, at 12:39 AM, Nicole Jacque via swift-dev
> wrote:
>
> As Ted Kremenek has previously announced, we are in the process of moving the
> Swift mailing lists to Discourse. Previously the discussion was mostly about
> moving swift-evolutio
