-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Mismatched closure arguments are no longer expanded in rustc 1.64 and later #100690
Comments
searched nightlies: from nightly-2022-06-01 to nightly-2022-08-11 bisected with cargo-bisect-rustc v0.6.4Host triple: x86_64-unknown-linux-gnu cargo bisect-rustc --prompt |
Looks like it was caused by #99539, which is pretty big diagnostics PR in that rollup. cc @compiler-errors |
Of course I caused it. |
@rustbot label -E-needs-bisection |
WG-prioritization assigning priority (Zulip discussion). @rustbot label -I-prioritize +P-medium |
…tebank Make `same_type_modulo_infer` a proper `TypeRelation` Specifically, this fixes rust-lang#100690 because we no longer consider a `ReLateBound` and a `ReVar` to be equal. `ReVar` can only be equal to free regions or static.
Sorry, this is not necessarily the smallest possible example. Please let me know if this is unhelpful and I'll come up with something more concise.
Given the following code: https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=8a1f669598035e38e7e141eb799d6738
The output in current stable (1.63.0) is:
(Please note the "expected closure with ... found closure with ..." hint.)
From 1.64 onwards, the expected/found hint is omitted:
To me the 1.63 behaviour is preferable to that from 1.64+ as it can often be non-obvious where the differences lie.
The text was updated successfully, but these errors were encountered: