Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upShow the location of a type usage for trait bound failures #66444
Comments
This comment has been minimized.
This comment has been minimized.
This is possibly addressed by @davidtwco's PR #65345 |
This comment has been minimized.
This comment has been minimized.
Assigning to myself, should get handled by #65345 but currently isn't (presumably due to this comment). @rustbot claim |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
cc @estebank
The following diagnostic doesn't tell the user anything about where the type that causes the failure is coming from. I understand that we can't report a correct source site, but we could create a heuristic:
Instead of having a
note:
without an associated span, we could check where (if at all) the type is used in the function and report those spans as potential sources of the error. Though I'm not sure what would be needed to fiddle this information through to the diagnostic reporting site.(Playground)
Errors: