<div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr">On Tue, Jul 19, 2016 at 9:00 AM Félix Cloutier <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Here's one way this could be implemented: if you write `struct Foo: Equatable` without implementing a `func ==`, the compiler makes one for you. Done.<br></blockquote><div><br></div><div>I floated a draft proposal a while back that addressed exactly this use case:</div><div><br></div><div><a href="https://gist.github.com/allevato/2fd10290bfa84accfbe977d8ac07daad">https://gist.github.com/allevato/2fd10290bfa84accfbe977d8ac07daad</a></div><div><br></div><div>It's purely additive so it's effectively shelved till post-Swift-3, and there are still some issues up for debate (the discussion thread was here <<a href="http://thread.gmane.org/gmane.comp.lang.swift.evolution/18495">http://thread.gmane.org/gmane.comp.lang.swift.evolution/18495</a>>), but it would likely address many of these concerns without going to the extreme of forbidding explicit implementation of Equatable or the other suggestions offered here (which I wouldn't support).</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Félix<br>
<br>
_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
</blockquote></div></div>