-
Notifications
You must be signed in to change notification settings - Fork 0
downcast regression: ambiguity due to global where-bounds #172
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
I believe this has to do with a disagreement in region responses between the param-env bound we get from elaborating This specifically requires that |
Worst case we wait until we get better w/ regions in responses 💀 Best case we come up with some better fix to the way we combine candidates when their region responses are practically equal. (At least, I think that's the case here). |
…=compiler-errors drop global where-bounds before merging candidates fixes rust-lang/trait-system-refactor-initiative#172 r? `@compiler-errors`
…=compiler-errors drop global where-bounds before merging candidates fixes rust-lang/trait-system-refactor-initiative#172 r? ``@compiler-errors``
…=compiler-errors drop global where-bounds before merging candidates fixes rust-lang/trait-system-refactor-initiative#172 r? ```@compiler-errors```
Rollup merge of rust-lang#139791 - lcnr:ignore-global-where-bounds, r=compiler-errors drop global where-bounds before merging candidates fixes rust-lang/trait-system-refactor-initiative#172 r? ```@compiler-errors```
…-errors drop global where-bounds before merging candidates fixes rust-lang/trait-system-refactor-initiative#172 r? ```@compiler-errors```
https://crater-reports.s3.amazonaws.com/pr-133502-1/try%23fa8e241660363f48d64b66b05eea58c93ab828fb/reg/mockall-0.13.1/log.txt
The text was updated successfully, but these errors were encountered: