-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Never consider int and float vars for FnPtr
candidates
#109896
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
Merged
bors
merged 1 commit into
rust-lang:master
from
Noratrieb:integers-are-not-fn-ptrs-remember-this-dear-transmuter
Apr 4, 2023
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,10 @@ | ||
// check-pass | ||
trait MyCmp { | ||
fn cmp(&self) {} | ||
} | ||
impl MyCmp for f32 {} | ||
|
||
fn main() { | ||
// Ensure that `impl<F: FnPtr> Ord for F` is never considered for int and float infer vars. | ||
0.0.cmp(); | ||
} |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the only case I can think of that could still cause issues, I just hope this was already always ambiguous anyway 🤞.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tried to call a method on a ty infer var but that caused errors in typeck about not being able to do that
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
rust/compiler/rustc_trait_selection/src/traits/select/candidate_assembly.rs
Line 39 in 1767585
_: Trait
is always ambiguous, and similarly treating fresh vars here is also fine here, since we'll only get those from freshening ty vars.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, that's what I ran into as well, when trying to reproduce it w/o floats.
AFAIK you can't get it to pick a trait based on method name alone, without something like
Default::default().method()
or<_>::method
but those give up too early because of how ambiguous they are, only int/float inference vars go farther (because they represent an unresolved choice in a small finite set of types etc.).The fuzzier ideas I've had would involve guiding inference, but
_: FnPtr
will never succeed early enough to taint inference, and blocking inference would likely require associated types etc. - and the moment you pin down a trait,FnPtr
can only affect it through a blanket impl of your choice, which would also apply to all the existing types too (beforeFnPtr
was added).EDIT: @compiler-errors' reply while I was playing around with more ideas for potential triggers, kind of invalidates all of those silly ideas, so yeah don't mind me, heh.