Is there already a swift-evolution proposal to have Optional conform to Hashable?
Conversation
Seems hard to do well in general. What should nil.hashValue be? If always “0”, that might create tons of collisions…
1
1
Isn’t it the case that `nil == nil` though?
1
2
Yeah, totally. I’m off base here!
what about generics? Would you have a need to compare a nil optional string and int?
1
I know they’d be different, but where does that difference manifest itself? In ==?