[swift-evolution] Implicit Optionals for Tuples & Tuples as Function Parameter

[Hooman Mehr]

Since Swift 3.0, they are no longer a normal type like Optional<T>. See SR-0054 <https://github.com/apple/swift-evolution/blob/master/proposals/0054-abolish-iuo.md>

> On Nov 11, 2016, at 11:54 AM, Muhammad Tahir Vali via swift-evolution <swift-evolution at swift.org> wrote:
> 
> Im curious to know the reasoning behind why implicit-wrapped optionals aren't allowed when creating tuples. Below is an example with type aliases and anonymous tuples.
> 
> ex. 
> typealias Name = (first: String!, middle: String?, last: String!)
> typealias Name = (first: String!, middle: String?, last: String!)!
> var name : (first: String!, middle: String?, last: String!)
> var name : (first: String!, middle: String?, last: String!)!
> 
> error from all 4 examples above:
> Implicitly unwrapped optionals are only allowed at top level and as function results
> 
> 
> I also noticed that I can modify tuples using functions ONLY if I use inout. 
> 
> func name(Person : inout (first: String?, middle: String?, last: String?)) {
>     Person.first = "John"
>     Person.last = "Doe"
> }
> 
> OR 
> 
> func name(Person : inout Name) {
>     Person.first = "John"
>     Person.last = "Doe"
> }
> 
> This is because tuples are passed into functions as 'let' constants. Why not add the ability to modify a copy of the tuple inside the function ?
> 
> 
> -- 
> Best Regards,
> 
> Muhammad T. Vali
> _______________________________________________
> 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/20161111/30fe4840/attachment.html>