[swift-evolution] Synthesizing Equatable, Hashable, and Comparable for tuple types

Mike Kluev mike.kluev at gmail.com
Sat Nov 25 06:35:40 CST 2017

On 25 November 2017 at 03:12, Xiaodi Wu <xiaodi.wu at gmail.com> wrote:

> On Fri, Nov 24, 2017 at 9:08 PM, Mike Kluev via swift-evolution <
> swift-evolution at swift.org> wrote:
>> On 24 November 2017 at 23:47, Douglas Gregor <dgregor at apple.com> wrote:
>>> e.g., making all tuples of Equatable elements Equatable
>> that's already the case.. (all tuples of equatable elements are
>> equatable). no?
> No, tuples do not conform to any protocols. There are hardcoded
> implementations of `==` up to some arity in the stdlib to partially
> mitigate the lack of protocol conformance.
to me as a user the end result is the same...
probably we need a better convincing example of what users may want that
doesn't have a workaround now.

speaking of ugliness, the ellipsis on the left of names is quite ugly:

     extension<...Elements : Equatable> (Elements...) : Equatable

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

More information about the swift-evolution mailing list