<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On May 24, 2016, at 6:50 PM, Tony Allevato wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Georgia; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">On the one hand, getting the conformance implicitly matches how<br>RawRepresentable is already treated, and makes getting the conformance zero<br>effort. On the other hand, it makes error handling trickier: if you add a<br>non-Equatable/non-Hashable field or associated value to a struct/enum, all<br>of your call sites break. (I guess they would even if you declared the<br>conformance, but at least there you'd also get the "Type does not conform<br>to Equatable/Hashable" error at the struct/enum itself, and the compiler<br>could even potentially flag the offending field/associated value that's<br>causing the conformance to fail.) Thoughts?<br></span></blockquote><br></div><div>I would like to have the option to override the compiler-provided equality etc.</div><div>For example, exclude one field from the definition of equality.</div><div>It would be nice if the default implementation would be available inside the definition of a custom implementation so you can base your custom implementation on that.</div><div><br></div><div>Jan E.</div><br></body></html>