<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Feb 19, 2016, at 7:45 AM, Sean Heber via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">I constantly run into this and I’m working on a Swift-only game project where I use value types as much as possible - but even there I find myself having to implement Equatable and Hashable on classes all the time just to add an == operator that just calls through to === / ObjectIdentity to get it to the work the way I need it to. Swift does a pretty good job eliminating boilerplate, but this is one area where it seems to stick out.<br class=""><br class="">It might be potentially awesome to be able to do something like this and have the compiler generate an == function for me using the given function:<br class=""><br class="">class MyClass: Equatable(===) {<br class="">// etc..<br class="">}<br class=""><br class="">But there are likely ramifications to this that I’m not really thinking about.<br class=""></div></div></blockquote></div><br class=""><div class="">You could provide a default implementation constrained on `AnyObject`:</div><div class=""><br class=""></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class="">func ==<T: AnyObject>(x: T, y: T) -> Bool { return x === y }</div></blockquote><div class=""><br class=""></div><div class="">Then you just need to declare `class MyClass: Equatable` to pick up that implementation for Equatable conformance.</div><div class=""><br class=""></div><div class="">-Joe</div><div class=""><br class=""></div><div class=""><br class=""></div></body></html>