You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, implicit conversion to a dummy _AnyHashable existential is being used as a workaround for being able to use any Hashable type as a key into a dictionary of AnyHashable
If generic subscripts are implemented, these could be eliminated.
The text was updated successfully, but these errors were encountered:
I didn't realize the goal was to remove the implicit conversion. Recently I made a patch to remove the subscript instead since it seemed redundant. But we could put them back, and disable the implicit conversion in Swift 4 mode. This would require an evolution proposal though. Is this still something you want to pursue or shall we just close this?
I have a question about AnyHashable:
Found it's ok to use it as a function argument type and swift implicitly boxes any Hashable I provide there (like it does for dictionaries).
Can I be sure in such behaviour?
Additional Detail from JIRA
md5: 945fe94ade9f9a0144335bf92d3ff4be
is blocked by:
Issue Description:
Currently, implicit conversion to a dummy
_AnyHashable
existential is being used as a workaround for being able to use anyHashable
type as a key into a dictionary ofAnyHashable
If generic subscripts are implemented, these could be eliminated.
The text was updated successfully, but these errors were encountered: