Is there already a swift-evolution proposal to have Optional conform to Hashable?
Conversation
Replying to
Seems hard to do well in general. What should nil.hashValue be? If always “0”, that might create tons of collisions…
Yeah, totally. I’m off base here!
1
Show replies