-
Notifications
You must be signed in to change notification settings - Fork 13.3k
$a:tt $($b:tt)*
is forbidden in macros
#25436
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
Labels
A-macros
Area: All kinds of macros (custom derive, macro_rules!, proc macros, ..)
E-easy
Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
E-mentor
Call for participation: This issue has a mentor. Use #t-compiler/help on Zulip for discussion.
I-ICE
Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️
P-medium
Medium priority
Comments
triage: P-medium |
I'd be happy to mentor this, if I don't fix it first. |
triage: P-medium |
cc @cmr |
I-ICE? |
nikomatsakis
added a commit
to nikomatsakis/rust
that referenced
this issue
May 15, 2015
Curious why this was closed, looks like it's blocking lispy-rust. |
@bjadamson It was fixed by #25444; do you still see this issue present in nightly? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-macros
Area: All kinds of macros (custom derive, macro_rules!, proc macros, ..)
E-easy
Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
E-mentor
Call for participation: This issue has a mentor. Use #t-compiler/help on Zulip for discussion.
I-ICE
Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️
P-medium
Medium priority
In an example like http://is.gd/TKfdKf:
we report the following error:
This is part of the macro future-proofing code but it is an unnecessary limitation. For fragments that represent at most one token tree (
tt
,block
,ident
, possibly others) there is no concern at all about being following by sequence repetition. This turns out to be a really big limitation in practice, since making macros that work over a generic sequence of token trees effectively allows for arbitrary parsing.cc @pnkfelix
The text was updated successfully, but these errors were encountered: