<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><br></div><div>On 08 Mar 2016, at 23:15, Austin Zheng via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr">I would prefer Equatable and Hashable to remain opt-in, and for us to add better support for automatic deriving of implementation.</div></div></blockquote><br><div><div><font color="#000000"><span style="background-color: rgba(255, 255, 255, 0);">On 08 Mar 2016, at 23:57, Zach Waldowski via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br><br></span></font></div><blockquote type="cite"><div><font color="#000000"><span style="background-color: rgba(255, 255, 255, 0);">I completely agree with Austin here. Automatic derivation (perhaps through the same mechanisms Joe is talking about) would be a nice enhancement, but I find it refreshing and advantageous for simple value types to have very little automatic behavior.</span></font></div></blockquote><br></div><div>Pedantically I agree with both of you, but from a very pragmatic point of you, I think it's very important to point out what Joe said about how this could reduce one of the most frustrating aspects of Swift, when people work with heterogeneous arrays and try to conform to Equatable:</div><div><br></div><div><blockquote type="cite"><span style="background-color: rgba(255, 255, 255, 0);">that would solve many of the common problems people currently have trying to work with heterogeneous containers.</span></blockquote></div><div><br></div><div><br></div></body></html>