-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Inference regression in 1.26 #49944
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
cc @nikomatsakis -- I think you wanted to at least be aware of these regressions. We'll probably be closing this though as it looks minimally impactful. |
Hmm. Thanks. I'm not sure what would cause that off top of my head. |
visiting for triage. @pietroalbini are you in a position to provide a standalone, minimized test case to speed up our ability to jump on this? |
triage: P-high (for now, since its a stable-to-beta regression, though @Mark-Simulacrum commented above that the impact may be "minimal" so who knows, it might get downgraded real soon...) |
Bisect points at #49163 (wut?), cc @SimonSapin |
let closest_to = |d| {
let gt = perfs.range(d..).next();
let lt = perfs.range(..d).next_back(); This closure passes |
I think this is business as usual when adding new impls. It is a minor change per https://github.com/rust-lang/rfcs/blob/master/text/1105-api-evolution.md#minor-change-implementing-any-non-fundamental-trait since the closure can be changed to |
Since the crate is now fixed and the breakage was minor and expected, I'm closing this. Thanks to everyone involved on this! |
There is an inference regression for a rust project.
The text was updated successfully, but these errors were encountered: