[swift-evolution] [Proposal][Discussion] Deprecate Tuple Shuffles

[Erica Sadun]

> On May 4, 2017, at 8:14 PM, Robert Widmann via swift-evolution <swift-evolution at swift.org> wrote:
> 
> Hi all,
> 
> So sorry that this proposal comes so late in the game, but I feel it’s too important not to bring it to the attention of the community now.  Attached is a proposal to deprecate a language feature many of you will probably have never had the chance to use: Tuple Shuffles.  I’ve attached a copy of the first draft of the proposal below, but the latest copy can be read on Github <https://github.com/apple/swift-evolution/pull/705/files>.
> 
> Thanks!
> 
> ~Robert Widmann
> 

I'm coming into this ridiculously late. Apologies, but I've had family responsibilities. I've tried to read through the thread before replaying. I hope I have not missed any significant points.

First, I dislike calling this "tuple shuffles". That phrase has an existing and useful meaning in the Swift community. It refers to what this proposal calls "re-assignment through a tuple pattern". This is what I want to keep calling a "tuple shuffle":

`(a, b, c) = (b, c, a)`

I'd rather call the problem space for this proposal "label-led tuple assignment" (or something like that) and reserve "tuple shuffle" for reordered value reassignment.

Second, I agree with TJ. I dislike that this pattern is legal:

```
// Declare using labels
let rgba: (r: Int, g: Int, b: Int, a: Int) = (255, 255, 255, 0)

// Declare using re-ordered labels
let argb: (a: Int, r: Int, g: Int, b: Int) = rgba // This is the line I have issue with

print(argb.a) // "0"
```

I find this usage counter to Swift's philosophy of clarity and simplicity. It is sufficiently obscure that I consider it a non-standard use regardless of Wux's  Google search results. 

Consider the example of Joe Groff's SE-0060 (https://github.com/apple/swift-evolution/blob/master/proposals/0060-defaulted-parameter-order.md <https://github.com/apple/swift-evolution/blob/master/proposals/0060-defaulted-parameter-order.md>). I believe it's reasonable to mandate that the order of labels in declarations be ignored, with the types being compiler-checked.  I'd envision that the "correct" behavior should act like this instead:

```
// Declare using re-ordered labels
let argb: (a: Int, r: Int, g: Int, b: Int) = rgba // (Int, Int, Int, Int) assigned to (Int, Int, Int, Int)

print(argb.a) // "255"
```

This reworking is partially inspired by SE-0111 (https://github.com/apple/swift-evolution/blob/master/proposals/0111-remove-arg-label-type-significance.md <https://github.com/apple/swift-evolution/blob/master/proposals/0111-remove-arg-label-type-significance.md>), ensuring that the tuple argument labels are not considered in typing the new constant. In fact, this entire proposal might be better named "Removing the Ordering Significance of Tuple Argument Labels in Declarations"

-- E

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20170508/81616731/attachment.html>