{"id":38796,"date":"2023-03-17T14:03:51","date_gmt":"2023-03-17T18:03:51","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=38796"},"modified":"2023-08-09T15:48:16","modified_gmt":"2023-08-09T19:48:16","slug":"equality-in-swift-nsobject-subclasses-and-existentials","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2023\/03\/17\/equality-in-swift-nsobject-subclasses-and-existentials\/","title":{"rendered":"Equality in Swift: NSObject, Subclasses, and Existentials"},"content":{"rendered":"

Mark Newton<\/a>:<\/p>\n

Conformance to the Equatable<\/code> protocol seems pretty straightforward. You simply override the ==<\/code> function.<\/p>

[…]<\/p>

This works great for objects like structs, or classes with no superclass. However, we can run into problems with the ==<\/code> function if we’re dealing with NSObject<\/code> subclasses.<\/p><\/blockquote>\n\n

Jayesh Kawli<\/a> (via Marcin Krzyzanowski<\/a>):<\/p>\n

And now if you try to do following comparison, they will either won’t work, will be buggy or fail to compile<\/p><\/blockquote>\n\n

Noah Gilmore<\/a>:<\/p>\n

\n

Swift can be tricky sometimes. For example, what does the following print?<\/p>\n

class A: NSObject {\n  let x: Int\n\n  init(x: Int) {\n    self.x = x\n  }\n}\n\nfunc ==(left: A, right: A) -> Bool {\n  return left.x == right.x\n}\n\nprint(A(x: 1) == A(x: 1))\nprint([A(x: 1)] == [A(x: 1)])\n<\/pre>\n
[…]<\/p>\n
The best way to make an NSObject<\/code> subclass use custom equality inside an array is to override isEqual:<\/code>[…]<\/p>\n<\/blockquote>\n
His reasoning for why the custom ==<\/code> didn’t work as expected is wrong<\/a>, but the solution<\/a> is correct. Similarly, you should override hashValue<\/code><\/a> (not hash(into:)<\/code>) if you need to change how it is Hashable<\/code>.<\/p>\n\n
For non-NSObject<\/code> classes, a similar issue applies. If you have something like:<\/p>\n
class Base: Equatable {\n    static func == (lhs: Base, rhs: Base) -> Bool {\n        return lhs === rhs\n    }\n}\n\nclass A: Base {\n    let x: Int\n\n    init(x: Int) {\n      self.x = x\n    }\n}\n\nfunc ==(left: A, right: A) -> Bool {\n    return left.x == right.x\n}<\/pre>\n
The results may not be what you expect:<\/p>\n
A(x: 1) == A(x: 1) \/\/ true\n[A(x: 1)] == [A(x: 1)] \/\/ false<\/pre>\n\n
Array<\/code> uses the ==<\/code> from where its elements conformed to Equatable<\/code>.<\/p>\n\n\n
Natalia Panferova<\/a> (tweet<\/a>):<\/p>\n
In Swift 5.7 that comes with Xcode 14 we can more easily check if two values of type Any<\/code> are equal, because we can cast values to any Equatable<\/code> and also use any Equatable<\/code> as a parameter type thanks to Unlock existentials for all protocols<\/a> change.<\/p>
[…]<\/p>
Inside isEqual()<\/code> method we have access to Self<\/code>, so we can try to cast the other<\/code> value to the same type as the concrete type of the value this method is called on. If the cast fails, the two values cannot be equal, so we return false<\/code>. If it succeeds, then we can check the two values for equality, using ==<\/code> function on values of the same concrete type.<\/p><\/blockquote>\n
There are some edge cases to be aware of, however, so it is preferred to use AnyHashable<\/code><\/a>.<\/p>\n\n
Ben Cohen<\/a>:<\/p>\n
You can define something similar for Comparable<\/code>[…]<\/p><\/blockquote>\n\n
Previously:<\/p>\n