Skip to content

Conversation

locallycompact
Copy link
Collaborator

No description provided.

@snoyberg
Copy link
Collaborator

I think we left these out because they tended to cause a lot of naming conflicts. But we included Hashable itself because it was useful in adding constraints. Since using the methods directly is so uncommon, I'd lean towards exposing these from outside of the RIO module itself, such as in RIO.Hashable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants