Skip to content

Diagnostic: resolve bare fn in expected closure #18409

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
Oct 31, 2014

Conversation

gamazeps
Copy link
Contributor

Closes #15273 (I did not find how to get the identifier in the message :/ ... if someone knows how to do that I would be happy to rebase)

Also creates the span_help! macro associated with #18126

Closes rust-lang#15273 (I did not find how to get the identifier in the message
:/)

Also creates the span_help! macro associated with rust-lang#18126
@alexcrichton
Copy link
Member

r? @pnkfelix

@pnkfelix
Copy link
Member

@gamazeps out of curiosity, why did you use span_help instead of span_note ?

@pnkfelix
Copy link
Member

@gamazeps oh never mind, I should have looked at #18126 first.

@gamazeps
Copy link
Contributor Author

@pnkfelix I stumbled upon that issue by random and I thought iit might be a good idea to start using the help span, but if you want i can go back to a note ?

alexcrichton added a commit to alexcrichton/rust that referenced this pull request Oct 30, 2014
@bors bors merged commit cb5f979 into rust-lang:master Oct 31, 2014
@gamazeps gamazeps deleted the issue15273 branch May 7, 2017 14:52
lnicola pushed a commit to lnicola/rust that referenced this pull request Oct 29, 2024
…umvx

Only construct a resolver in macro descension when needed
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.

improve err msg for "cannot coerce non-statically resolved bare fn"
4 participants