-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
detect wrong number of args when type-checking a closure #48123
detect wrong number of args when type-checking a closure #48123
Conversation
b32530a
to
1306c37
Compare
I should add: I'm not terribly happy with how the error reporting code is organized. It feels rather haphazard. I think we should think about exacting the code in |
☔ The latest upstream changes (presumably #48113) made this pull request unmergeable. Please resolve the merge conflicts. |
r=me after fixing rebasing and making travis happy. Don't think that having no output for issue-47706-trait is valid.
|
1306c37
to
00ce422
Compare
Instead of creating inference variables for those argument types, use the trait error-reporting code to give a nicer error.
00ce422
to
cc05561
Compare
@bors r=estebank |
📌 Commit cc05561 has been approved by |
…um-args, r=estebank detect wrong number of args when type-checking a closure Instead of creating inference variables for those argument types, use the trait error-reporting code to give a nicer error. This also improves some other spans for existing tests. Fixes rust-lang#47244 r? @estebank
…um-args, r=estebank detect wrong number of args when type-checking a closure Instead of creating inference variables for those argument types, use the trait error-reporting code to give a nicer error. This also improves some other spans for existing tests. Fixes rust-lang#47244 r? @estebank
…um-args, r=estebank Fixes rust-lang#47311. r? @nrc
…um-args, r=estebank detect wrong number of args when type-checking a closure Instead of creating inference variables for those argument types, use the trait error-reporting code to give a nicer error. This also improves some other spans for existing tests. Fixes rust-lang#47244 r? @estebank
Instead of creating inference variables for those argument types, use
the trait error-reporting code to give a nicer error. This also
improves some other spans for existing tests.
Fixes #47244
r? @estebank