# SE-0266 — Synthesized  Comparable  conformance for enum types

**URL:** <https://forums.swift.org/t/se-0266-synthesized-comparable-conformance-for-enum-types/29457>\
**Category:** Proposal Reviews\
**Created:** [October 2, 2019, 12:01am UTC](https://forums.swift.org/t/se-0266-synthesized-comparable-conformance-for-enum-types/29457 "2019-10-02T00:01:34Z")\
**Posts on this page:** 1\
**Showing post:** 27

<div class="post-metadata">

**Author:** ![anandabits](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/anandabits/32/355_2.png) [@anandabits](https://forums.swift.org/u/anandabits)\
**Post date:** [October 2, 2019, 5:35pm UTC](https://forums.swift.org/t/se-0266-synthesized-comparable-conformance-for-enum-types/29457/27 "2019-10-02T17:35:09Z")

</div>

> [@allevato](#):
>
> you can't reorder the associated values of an enum case declaration and retain source compatibility with the usage sites

This is the strongest argument I've seen so far, but it comes with the memberwise initializer exception you note. `public` synthesized member wise initializers have frequently requested. My [latest pitch on this topic](https://forums.swift.org/t/explicit-memberwise-initializers/22893) was well received.

> [@allevato](#):
>
> I think it's still consistent to tie `Comparable` synthesis to things that can be reordered in source without affecting public API/source compatibility

What do you mean by this? Enum cases can be reordered without breaking source and associated values cannot, so your meaning isn't entirely clear.

---

_[View the full topic](https://forums.swift.org/t/se-0266-synthesized-comparable-conformance-for-enum-types/29457)._
