Extending CGPoint to conform to Hashable
I can see no advantage of computing the hash value from Int(self.x) and Int(self.y). As you already noticed, truncating the floating point
numbers to integers loses information and therefore causes
hash collisions.
CGFloat is (like all Swift number point types) Hashable, and its
hashValue is just the integer with the same memory representation
(as one can see from the implementation). So all possible CGFloat values have different hash values, which makes x.hashValue, y.hashValue a much better basis for computing a hash value for CGPoint than
Int(self.x) and Int(self.y).
It remains the question how to compute the hash value of the point
from the hash values of its coordinates. Of course there can be no
&quot;best hash&quot; which works for all data sets. But in order to get
at least an idea which might be better or worse, I used the
following simple test:
var hv = Set&lt;Int&gt;()
var count = 0
for i in -200 ..&lt; 200 {
    for j in -200 ..&lt; 200 {
        count += 1
        let p = CGPoint(x: CGFloat(i)/20, y: CGFloat(j)/20)
        hv.insert(p.hashValue)
    }
}

print(count, hv.count)

It computes the hash values of 160,000 points where both
x and y range from -20 to 19.9 in steps of 0.1, and counts
how many different hash values we get.
The referenced hash function from here,
translated to Swift 3, is
public var hashValue: Int {
    return (self.x.hashValue &lt;&lt; MemoryLayout&lt;CGFloat&gt;.size) ^ self.y.hashValue
}
// # of points: 160000 hash values:  79976

Your hash function is definitely worse (but we already know why):
public var hashValue: Int {
    var hash = 23
    hash = hash &amp;* 31 &amp;+ Int(self.x)
    return hash &amp;* 31 &amp;+ Int(self.y)
}
// # of points: 160000 hash values:  1249

Using hashValue instead of Int() improves it considerably:
public var hashValue: Int {
    var hash = 23
    hash = hash &amp;* 31 &amp;+ self.x.hashValue
    return hash &amp;* 31 &amp;+ self.y.hashValue
}
// # of points: 160000 hash values:  68827

But this is still not really satisfying.
The Boost library has a hash_combine()
function for exactly this purpose, and its implementation
has one generic variant
template &lt;typename SizeT&gt;
inline void hash_combine_impl(SizeT&amp; seed, SizeT value)
{
    seed ^= value + 0x9e3779b9 + (seed&lt;&lt;6) + (seed&gt;&gt;2);
}

as well as specializations for uint32_t and uint64_t.
Translated to Swift this would be:
func hash_combine(seed: inout UInt, value: UInt) {
    let tmp = value &amp;+ 0x9e3779b9 &amp;+ (seed &lt;&lt; 6) &amp;+ (seed &gt;&gt; 2)
    seed ^= tmp
}

It is crucial here to use unsigned integers, otherwise
the right shift seed &gt;&gt; 2 would preserve the sign bit.
The Swift hashValue is a signed integer, however, therefore
we have to convert accordingly:
public var hashValue: Int {
    var seed = UInt(0)
    hash_combine(seed: &amp;seed, value: UInt(bitPattern: x.hashValue))
    hash_combine(seed: &amp;seed, value: UInt(bitPattern: y.hashValue))
    return Int(bitPattern: seed)
}
// # of points: 160000 hash values:  159958

As one can see, this hash function has only 42 collisions, and is
far better than the previous ones (for this data set). It is also relatively simple to compute, and can easily be adapted
for types with more properties.
If that is not good enough then you can try other &quot;hash combine&quot; methods,
for example the the 32-bit or
64-bit specializations from the Boost library (depending on the
size of Int on your platform) and check if that works better.
Another one is
here,
and there are probably much more.
Finally you asked:

Or, would the best approach not even be to extend CGPoint at all and to just use a custom Swift container struct or an NSObject subclass?

It depends. If the tuple represents a &quot;point in space&quot; then using (and
extending) CGPoint seems fine to me. If the tuple represents something
else (and you just chose CGPoint because it happens to have two
properties) then I would prefer to define a custom struct which
clearly shows its purpose. A subclass of NSObject would be a
reference type and should only be chosen if you need reference
semantics. Otherwise value types are preferable.

Update: As of Swift 4.1, the compiler can synthesize the
conformance to Equatable/Hashable if all of its members are Equatable/Hashable, see SE-0185 Synthesizing Equatable and Hashable conformance.
Example:
struct Point : Hashable {
    let x: CGFloat
    let y: CGFloat
}

The actual hash function is an implementation detail, but in my test
it worked excellently: The above test code produced no collisions at all
for the 160,000 points.