[Returned for revision] SE-0283: Tuples Conform to Equatable, Comparable, and Hashable

Evolution Announcements
1

Hello, Swift community.

SE-0283: Tuples Conform to Equatable, Comparable, and Hashable was reviewed in May of 2020 and ultimately accepted. Five and a years have now passed, and the feature has never been released. While the LSG still believes that tuple types ought to conform to these protocols, it is long overdue that we acknowledge the original acceptance as defunct. The world of Swift has changed a lot in the last five years, especially with the introduction of variadic generics. The LSG is therefore returning SE-0283 for revision to consider whether it is still viable and explore how it ought to work in the language as it exists today.

This is just bookkeeping. We are not giving up on tuple conformances, but we are also not aware of anyone currently working on them. The LSG is just trying to make this proposal's formal status reflect the reality of its implementation.

John McCall
Language Steering Group (chair)

20 Likes
2

Great to see someone picking the proposal up again. I was wondering why it was never implemented. I assume it wasn't important enough at the time, with the whole Swift Concurrency implementation, I assume?

3

To clarify: we are not aware of anyone picking up work on this--it is just a bookkeeping announcement because there have been questions, including recently, on its status.

1 Like
4

Thanks for the clarification, I just found the additional commentary and User-defined tuple conformances pitch

1 Like
5

it would be great if this was finally implemented. This has been an annoying paper cut for some time ^^