E0283 error explain #28469
E0283 error explain #28469
Conversation
|
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. 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. |
|
I haven't this check fail locally. What to do? Fix and repeat? Are there another flaws in the PR? |
| @@ -1900,7 +1951,7 @@ register_diagnostics! { | |||
| E0278, // requirement is not satisfied | |||
| E0279, // requirement is not satisfied | |||
| E0280, // requirement is not satisfied | |||
| E0283, // cannot resolve type | |||
| // E0283, // cannot resolve type | |||
|
@deniskolodin Can you squash the commits? |
|
It looks complete. Something else? |
|
r? @Manishearth |
| } | ||
| ``` | ||
|
|
||
| Also you can use generic type if binding isn't ambiguous: |
There was a problem hiding this comment.
a generic type if the binding
I'm not actually sure what this comment is saying we should do, perhaps you meant "use a type hint"?
|
I've fixed text and removed the last example, because It offers another design, but not a solution. Check the result, please. |
| } | ||
| ``` | ||
|
|
||
| To resolve use the concrete type: |
There was a problem hiding this comment.
"To resolve this error use the concrete type:" instead seems better.
|
@bors: r+ rollup Sorry this took so long to get in, @deniskolodin |
|
📌 Commit 50b43f6 has been approved by |
No description provided.