Uh oh!
There was an error while loading. Please reload this page.
Add note to type mismatch errors related to specialization. - #33492
Add note to type mismatch errors related to specialization.#33492rphmeier wants to merge 1 commit into
Conversation
Specifically, default associated types cannot be projected as specific types.
rust-highfive
commented
May 8, 2016
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @Aatch (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. Please see the contribution instructions for more information. |
rphmeier
commented
May 8, 2016
It could also be beneficial to add a separate error code for this issue; I have a strategy in mind for doing so if it proves to be better. |
rphmeier
commented
May 9, 2016
cc @aturon |
bors
commented
May 11, 2016
☔ The latest upstream changes (presumably #33425) made this pull request unmergeable. Please resolve the merge conflicts. |
rphmeier
commented
May 12, 2016
Closing in favor of new PR. |
Specifically, default associated types cannot be projected as specific types.
Fixes#33481 (which was actually by design)