> On Mar 13, 2017, at 8:38 AM, Vincent Esche via swift-evolution
> <[email protected]> wrote:
>
> Hi there,
>
> I've written up a proposal for an overhaul/replacement of the Hashable
> protocol and would love to hear your feedback on it!
>
> Rendered
> <https://gist.github.com/regexident/1b8e84974da2243e5199e760508d2d25> | Blog
> Post <https://blog.definiteloops.com/ha-r-sh-visitors-8c0c3686a46f>
Are we committed to having `hashValue` always be an `Int`, or could it be an
associated type like `(Int, Int, Int, Int)`? Seems like especially for
something like a BigNum type or an Array, there might simple not be a
reasonably efficient way to uniquely-ish represent 1024 bits with just 64 bits.
(This kinda feels like one of those questions where the answer starts out with
a variation on “you’re missing the point”)
- Dave Sweeris
_______________________________________________
swift-evolution mailing list
[email protected]
https://lists.swift.org/mailman/listinfo/swift-evolution
