-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Clean up E0283 explanation #69007
Clean up E0283 explanation #69007
Conversation
@@ -1,7 +1,7 @@ | |||
This error occurs when the compiler doesn't have enough information | |||
to unambiguously choose an implementation. | |||
An implementation cannot be chose unambiguously because of the lack of |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
An implementation cannot be chose unambiguously because of the lack of | |
An implementation cannot be chosen unambiguously because of lack of |
@@ -27,7 +27,9 @@ fn main() { | |||
} | |||
``` | |||
|
|||
To resolve this error use the concrete type: | |||
This error can be solved by adding type annotations to give the missing |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This error can be solved by adding type annotations to give the missing | |
This error can be solved by adding type annotations that provide the missing |
@@ -27,7 +27,9 @@ fn main() { | |||
} | |||
``` | |||
|
|||
To resolve this error use the concrete type: | |||
This error can be solved by adding type annotations to give the missing | |||
information to the compier. In this case, the solution is to use a concrete |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
information to the compier. In this case, the solution is to use a concrete | |
information to the compiler. In this case, the solution is to use a concrete |
Updated! |
e5f6d97
to
ded6292
Compare
@bors r+ rollup |
📌 Commit ded6292 has been approved by |
…lan-DPC Clean up E0283 explanation r? @Dylan-DPC
Rollup of 6 pull requests Successful merges: - #68897 (clean up E0275 explanation) - #68908 (Add long error code explanation message for E0637 ) - #68932 (self-profile: Support arguments for generic_activities.) - #68986 (Make ASCII ctype functions unstably const ) - #69007 (Clean up E0283 explanation) - #69014 (change an instance of span_bug() to struct_span_err() to avoid ICE) Failed merges: r? @ghost
Rollup of 6 pull requests Successful merges: - #68897 (clean up E0275 explanation) - #68908 (Add long error code explanation message for E0637 ) - #68932 (self-profile: Support arguments for generic_activities.) - #68986 (Make ASCII ctype functions unstably const ) - #69007 (Clean up E0283 explanation) - #69014 (change an instance of span_bug() to struct_span_err() to avoid ICE) Failed merges: r? @ghost
r? @Dylan-DPC