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.

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

Type inference for overloadable operators #2454

Closed
flodiebold opened this issue Nov 30, 2019 · 3 comments
Closed

Type inference for overloadable operators #2454

flodiebold opened this issue Nov 30, 2019 · 3 comments
Labels
A-ty type system / type inference / traits / method resolution S-unactionable Issue requires feedback, design decisions or is blocked on other work

Comments

@flodiebold
Copy link
Member

Follow-up to #390. We don't support overloads of the binary operators in the type system yet, e.g. handling custom Add implementations etc.. We have all the necessary systems in place to do this, but I don't know if it makes sense to try doing it before we've got a solution for rust-lang/chalk#234, since that would probably prevent many cases from working anyway.

@kiljacken kiljacken added the A-ty type system / type inference / traits / method resolution label Jan 10, 2020
@lnicola lnicola added the S-unactionable Issue requires feedback, design decisions or is blocked on other work label Jan 25, 2021
@flodiebold
Copy link
Member Author

This is mostly implemented, except for some bugs (#7150).

@rben01
Copy link

rben01 commented Dec 3, 2022

If RA reports that the inferred type of 1_u32 / 2_u32 is <u32 as Div<u32>>::Output, does that fall under this issue, or should I submit a separate issue? (I'd expect u32 due to the trait implementation here, which AFAIK is unambiguous.)

@Veykril
Copy link
Member

Veykril commented Dec 3, 2022

That seems to be a problem with your rust setup or project

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-ty type system / type inference / traits / method resolution S-unactionable Issue requires feedback, design decisions or is blocked on other work
Projects
None yet
Development

No branches or pull requests

5 participants