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
Error handling for macros #916
Conversation
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.
overall, lgtm, but let's try to separate parsing & expansion errors. And perhaps it would be a good idea to write some unit-tests for parsing and exapnsion of erroneous macros.
I've added some simple tests for error cases. The test organization could be better, but I didn't want to dump all tests in There's also some weirdness with |
Excellent, bors r+ |
bors r+ |
Build succeeded |
A next step would be to fix
logic. This is for handling repeates: if
It would be cool to dig into the rustc implementation and figure out to handle this properly. The useful bits of rustc are:
|
Part of #720