-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Can't compare unsafe function pointers #13385
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
Previously `extern` functions up to arity 5 had `PartialEq` implementations in libcore, but this doesn't handle comparing against `unsafe` functions, or larger arity functions. Fixes rust-lang#13385.
I wrote some code over in #14719, but @alexcrichton points out some edge cases that it would be good to properly spec. This can/should probably go through an RFC. |
I'm pulling a massive triage effort to get us ready for 1.0. As part of this, I'm moving stuff that's wishlist-like to the RFCs repo, as that's where major new things should get discussed/prioritized. This issue has been moved to the RFCs repo: rust-lang/rfcs#718 |
Don't report build-scripts and proc-macros as metadata progress Seems somewhat confusing to me, given `metadata` is already the step we do for workspace loading
yields
The text was updated successfully, but these errors were encountered: