# Tuples conform to Equatable

**URL:** <https://forums.swift.org/t/tuples-conform-to-equatable/32559>\
**Category:** Pitches\
**Created:** [January 14, 2020, 1:58am UTC](https://forums.swift.org/t/tuples-conform-to-equatable/32559 "2020-01-14T01:58:41Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![xwu](https://avatars.discourse-cdn.com/v4/letter/x/b487fb/32.png) [@xwu](https://forums.swift.org/u/xwu)\
**Post date:** [January 14, 2020, 11:16am UTC](https://forums.swift.org/t/tuples-conform-to-equatable/32559/9 "2020-01-14T11:16:40Z")

</div>

> [@Alejandro](#):
>
> Correct, nobody can currently _write_ an Equatable conformance for some tuple type, and yes, there is no semantic difference. If this is accepted, all clients who currently use `==` for tuples that compile against this new compiler + runtime will reference the Equatable implementation vs. using the stdlib `==` for tuples. That's it, just some machinery in the background working.

Question—if this is accepted, and a resilient library makes use of magically generated tuple equality, will it be an ABI-breaking change in a future version of Swift to implement a custom conformance when it becomes possible to do so?

---

_[View the full topic](https://forums.swift.org/t/tuples-conform-to-equatable/32559)._