-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Cross-crate overloading doesn't work #2615
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
Comments
Do we know this is the case? I'm pretty sure we are using this now. |
I assumed this was true because |
I've got a bunch of code that implements + for [T] as an iface. I haven't noticed any cross-crate problems with it. I think we had some problems along these lines when I started this summer though. |
Ok, well, I still want there to be at least one test case (possibly an existing one) before I close this! |
I wrote that because @nikomatsakis had said he had found a bunch of issues with it, mainly in reachability checking IIRC (although I also remember he had trouble reproducing them). Paging him. |
These problems may have been fixed in the meantime. They were quite easy to reproduce: remove the |
…2615 (cross-crate operator overloading).
Added a (working) test in 6a7c714; closing. |
point to my fork of josh for now This is the version of josh that I used to create rust-lang#103392.
point to my fork of josh for now This is the version of josh that I used to create rust-lang#103392.
as per a FIXME in
core::num
The text was updated successfully, but these errors were encountered: