You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 8, 2024. It is now read-only.
i.e. the grammar for macro invocation should just be $ident ! ( $tt* ).
Any more information in the grammar would require back-information for what the macro definition is.
I do think that we should try to match productions to what the macro matchers accept, though this I think would be a soft rather than hard requirement. (macros 2.0 has some room to change what are matched.)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
How exactly will macros be handled?
Will the macro part of the grammar simply indicate token trees, or should there be more to it? What needs to be addressed here?
Will the grammar's rules exactly match what the different fragment specifier types (
expr
,stmt
, etc.) accept in rustc?The text was updated successfully, but these errors were encountered: