Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

find a better way to deal with the Equiv trait #5591

Closed
thestinger opened this issue Mar 27, 2013 · 1 comment
Closed

find a better way to deal with the Equiv trait #5591

thestinger opened this issue Mar 27, 2013 · 1 comment
Labels
A-frontend Area: Compiler frontend (errors, parsing and HIR)

Comments

@thestinger
Copy link
Contributor

Right now, core::hashmap has a find_equiv method in addition to find which is useful for situations like using &str for a lookup in a map with ~str keys instead of having to use &~str.

It would probably be better to add a type parameter to the comparison traits (TotalEq, etc.) and possibly allow x == y with different types on each side.
@thestinger
Copy link
Contributor Author

Closing in favour of #7088.

This was referenced Sep 30, 2022
Open
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-frontend Area: Compiler frontend (errors, parsing and HIR)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@thestinger