[swift-evolution] Making capturing semantics of local
Slava Pestov
spestov at apple.com
Thu Oct 26 23:54:37 CDT 2017
> On Oct 26, 2017, at 9:53 PM, Howard Lovatt via swift-evolution <swift-evolution at swift.org> wrote:
>
> It would be easy to provide a fixit.
That is still a source breaking change that requires migration, though.
> How often are they actually used? I rarely use them and all my use cases could be a closure instead.
>
> Also see Mike Kluev example; local functions are arguably worse than closures in all cases (provided that you can appropriately annotate the function type).
Closures cannot replace all uses of local functions. Local functions can be recursive, and have a generic parameter list.
Slava
>
> -- Howard.
>
> On 27 October 2017 at 12:26, Slava Pestov <spestov at apple.com <mailto:spestov at apple.com>> wrote:
>
>
>> On Oct 26, 2017, at 4:45 PM, Howard Lovatt via swift-evolution <swift-evolution at swift.org <mailto:swift-evolution at swift.org>> wrote:
>>
>> Rather than expand local function syntax why not deprecate local functions completely
>
> I don’t think at this point such a drastic change to the language is likely to happen.
>
> Slava
>
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20171026/dfa0f089/attachment.html>
More information about the swift-evolution
mailing list