Skip to content

librustc: Fix a couple of cases in which unboxed closure typechecking #16637

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

Merged
merged 1 commit into from
Aug 22, 2014

Conversation

pcwalton
Copy link
Contributor

code wasn't considering the zero-argument case.

Closes #16168.

r? @pnkfelix

code wasn't considering the zero-argument case.

Closes rust-lang#16168.
bors added a commit that referenced this pull request Aug 21, 2014
… r=pnkfelix

code wasn't considering the zero-argument case.

Closes #16168.

r? @pnkfelix
@bors bors closed this Aug 22, 2014
@bors bors merged commit 7f4c5be into rust-lang:master Aug 22, 2014
bors added a commit to rust-lang-ci/rust that referenced this pull request Feb 25, 2024
…r=Veykril

fix: Fix proc-macro server not accounting for string delimiters correctly

Fixes rust-lang/rust-analyzer#16622

Note that this is a bug a in the proc-macro server, so this won't be fixed until the next subtree sync
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Cannot call call_mut on an unboxed closure with no arguments due to type () not being ()
3 participants