[swift-evolution] Removing "_ in" from empty closures

Matthew Johnson matthew at anandabits.com
Fri May 13 15:06:18 CDT 2016


Is anyone planning to write a proposal for this?

Sent from my iPhone

> On May 13, 2016, at 3:02 PM, Jacob Bandes-Storch via swift-evolution <swift-evolution at swift.org> wrote:
> 
> +1, seems logical to me:
> 
>     let x: [T] = []
>     let x: [T:U] = [:]
>     let x: T->() = {}
> 
> Jacob
> 
>> On Fri, May 13, 2016 at 10:48 AM, Erica Sadun via swift-evolution <swift-evolution at swift.org> wrote:
>> On May 13, 2016, at 11:14 AM, Cole Campbell via swift-evolution <swift-evolution at swift.org> wrote:
>> >
>> >
>> >> +1. In general, I think we should allow implicit arguments, without requiring the closure to use all the implicit $n variables like we do today. These should all be valid:
>> >>
>> >> let _: () -> () = {}
>> >> let _: (Int) -> () = {}
>> >> let _: (Int, Int) -> Int = { 5 }
>> >> let _: (Int, Int) -> Int = { $0 }
>> >> let _: (Int, Int) -> Int = { $1 }
>> >
>> > +1. This would be excellent.
>> 
>> +1. Good riddance to bad code baggage.
>> 
>> -- E
>> 
>> _______________________________________________
>> swift-evolution mailing list
>> swift-evolution at swift.org
>> https://lists.swift.org/mailman/listinfo/swift-evolution
> 
> _______________________________________________
> 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/20160513/edf1fd63/attachment.html>


More information about the swift-evolution mailing list