-
Notifications
You must be signed in to change notification settings - Fork 22
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
Pull solve_item_traits
out of mir_traits
#637
Comments
This issue has been marked as stale due to a lack of activity for 60 days. If you believe this issue is still relevant, please provide an update or comment to keep it open. Otherwise, it will be closed in 7 days. |
This issue has been marked as stale due to a lack of activity for 60 days. If you believe this issue is still relevant, please provide an update or comment to keep it open. Otherwise, it will be closed in 7 days. |
@Nadrieril fixed that in #1031 :) |
#627 introduces a use of
mir_traits::solve_item_traits
in the extraction of types, which are common to THIR and MIR. Thussolve_item_traits
should move out ofmir_traits.rs
.solve_item_traits
should anyway be re-written using the traitsrustc_utils::SubstBinder
andrustc_utils::PredicateToPolyTraitRef
.The text was updated successfully, but these errors were encountered: