-
Notifications
You must be signed in to change notification settings - Fork 13.6k
remove FIXME block from has_significant_drop
, can handle inference
#145181
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
base: master
Are you sure you want to change the base?
Conversation
Let's double check this with crater. @bors2 try |
remove FIXME block from `has_significant_drop`, can handle inference
@craterbot check |
👌 Experiment ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more |
🚧 Experiment ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more |
I think the more likely thing here is that we're now being more responsible and only calling |
I did actually try this- the inference block I removed is certainly being hit in a few cases. I can rerun that experiment to find exactly which if you'd like. Are you thinking the related queries still don't cope with infer vars? If so, do you know of a way to test this? (locally, not with craterbot ofc) |
@compiler-errors https://github.com/rust-lang/rust/blob/master/tests/incremental/issue-86753.rs is an example for where I do see an argument for favoring canonicalization regardless- I just see this as an avenue for reducing complexity. Whatever seems to be the most appropriate. |
🎉 Experiment
|
The
FIXME
block inTy::has_significant_drop
is outdated as related queries can now handle type inference.rust/compiler/rustc_middle/src/ty/util.rs
Lines 1378 to 1389 in 321a89b
Closes #86868 (other places mentioned in the issue have been resolved, or moved to other issues)
r? types