Swift 4.2 strange behavior

There’s been discussions around this in the past. This is a consequence of the tuple shuffle feature, which I think is about to be put through evolution for removal. Deprecating Tuple Shuffles (Round 2)