-
Notifications
You must be signed in to change notification settings - Fork 13.3k
[RFC-3086] Consider out-of-bound depths of count
#111923
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
Conversation
r? @davidtwco (rustbot has picked a reviewer for you, use r? to override) |
r? compiler |
I'm on vacation and won't get to this before the 19th Also cc @petrochenkov for macro stuff |
@bors try |
⌛ Trying commit c218557ac737a43e768bd2736ead296b3fb6a7b5 with merge 5723d0448b9ce6bed8424358575f87427ecc6050... |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
@oli-obk
That said, I think a FCP isn't necessary. |
Oh I didn't realize that. I just saw the behaviour change... @craterbot cancel |
This comment was marked as outdated.
This comment was marked as outdated.
@craterbot abort |
This comment was marked as resolved.
This comment was marked as resolved.
⌛ Testing commit 0366888 with merge ce62cbcd4aba08c32632d7805d200eaf53a96a98... |
This comment has been minimized.
This comment has been minimized.
💔 Test failed - checks-actions |
Well, the matter needs more investigation on my side |
@rustbot author |
@bors r- bors synchronize queue fix |
@c410-f3r any updates on this? |
CI failure still can't be reproduced locally. @oli-obk Can you r? again so I can see the logs? All previous runs are now 404. |
Failed to set assignee to
|
@bors r+ |
[RFC-3086] Consider out-of-bound depths of `count` Fix rust-lang#111905 In the matching of macro calls and their respective declarations (transcribe), a warning is issued if `count` has a depth greater than the number of nested `NamedMatch`s through be verification of `MatchedSeq` with empty elements. Doesn't affect `( $( { $( [ $( ( $( $t:ident )* ) )* ] )* } )* ) => { ${count(t, 1)} }` called with `bar!( { [] [] } )` which will still continue to output `2`.
The job Click to see the possible cause of the failure (guessed by this bot)
|
💔 Test failed - checks-actions |
Thank you @oli-obk I spent several hours trying to find a solution and nothing worked. Now I don't have the time or motivation to continue pursuing this PR. |
Fix #111905
In the matching of macro calls and their respective declarations (transcribe), a warning is issued if
count
has a depth greater than the number of nestedNamedMatch
s through be verification ofMatchedSeq
with empty elements.Doesn't affect
( $( { $( [ $( ( $( $t:ident )* ) )* ] )* } )* ) => { ${count(t, 1)} }
called withbar!( { [] [] } )
which will still continue to output2
.