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 }}
Repository navigation
regression: local ambiguity: multiple parsing options: built-in NTs lifetime #70446
Possibly accidentally injected by #70074.
Would be good to find out why this is happening, so let's @rustbot ping cleanup
and see if we can bisect / shrink the problem down to something usable for finding a fix.
Hey Cleanup Crew ICE-breakers! This bug has been identified as a good
"Cleanup ICE-breaking candidate". In case it's useful, here are some instructions for tackling these sorts of bugs. Maybe take a look?
Thanks! <3
searched nightlies: from nightly-2020-02-26 to nightly-2020-03-04
regressed nightly: nightly-2020-02-29
searched commits: from https://github.com/rust-lang/rust/commit/6d69caba110c0c2fb90180df1cbc8be5033b91d4 to https://github.com/rust-lang/rust/commit/0eb878d2aa6e3a1cb315f3f328681b26bb4bffdb
regressed commit: https://github.com/rust-lang/rust/commit/0eb878d2aa6e3a1cb315f3f328681b26bb4bffdb
For code I used:
use pin_project_lite::pin_project;pin_project!{pubstructStruct<T:'static> {
field:T}}fnmain(){}
Compiling playground v0.0.1 (/playground)
error: local ambiguity: multiple parsing options: built-in NTs lifetime ('l') or path ('p').
--> src/main.rs:3:38
|
3 | => {m!{@internal $(: $p )? : $l }};
| ^^
...
8 | m! {: 'static}
| -------------- in this macro invocation
|
= note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
error: aborting due to previous error
error: could not compile `playground`.
To learn more, run the command again with --verbose.
error: local ambiguity: multiple parsing options: built-in NTs lifetime ('l') or path ('p').
--> src/lib.rs:2:66
|
2 | ($(: $p:path)? $(: $l:lifetime)? ) => { bar! {$(: $p)? $(: $l)? } };
| ^^
...
10 | foo! {: 'a }
| ------------ in this macro invocation
|
= note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
error: aborting due to previous error
I think we can now @rustbot modify labels: -E-needs-mcve
Activity
Centril commentedon Mar 26, 2020
Possibly accidentally injected by #70074.
Would be good to find out why this is happening, so let's @rustbot ping cleanup
and see if we can bisect / shrink the problem down to something usable for finding a fix.
Centril commentedon Mar 26, 2020
@rustbot ping cleanup
rustbot commentedon Mar 26, 2020
Hey Cleanup Crew ICE-breakers! This bug has been identified as a good
"Cleanup ICE-breaking candidate". In case it's useful, here are some
instructions for tackling these sorts of bugs. Maybe take a look?
Thanks! <3
cc @AminArria @chrissimpkins @contrun @DutchGhost @elshize @ethanboxx @h-michael @HallerPatrick @hdhoang @hellow554 @imtsuki @jakevossen5 @kanru @KarlK90 @LeSeulArtichaut @MAdrianMattocks @matheus-consoli @mental32 @nmccarty @Noah-Kennedy @pard68 @PeytonT @pierreN @Redblueflame @RobbieClarken @RobertoSnap @robjtede @SarthakSingh31 @senden9 @shekohex @sinato @spastorino @turboladen @woshilapin @yerke
LeSeulArtichaut commentedon Mar 26, 2020
Failed to confirm that #70074 is the cause:
tested 342c5f33d097b2dc07a2dbc0ca45a37379d2ff60, got YesSeems like it regressed prior to 342c5f3
AminArria commentedon Mar 26, 2020
For code I used:
LeSeulArtichaut commentedon Mar 26, 2020
@rustbot modify labels: -E-needs-bisection
LeSeulArtichaut commentedon Mar 26, 2020
My progress on an MCVE so far
steffahn commentedon Mar 26, 2020
Reduced example:
(Playground)
Errors:
LeSeulArtichaut commentedon Mar 26, 2020
Split the macro in two parts to make it easier to follow, and removed the special lifetime
'static:(Playground)
Error:
I think we can now @rustbot modify labels: -E-needs-mcve
LeSeulArtichaut commentedon Mar 26, 2020
I believe that the most probable culprit is #69384, cc @petrochenkov
LeSeulArtichaut commentedon Mar 27, 2020
#69384 is indeed the culprit, I can reproduce the bug on b2605c1
spastorino commentedon Apr 1, 2020
This was briefly discussed during pre-triage. Assigning
P-highfor now until we have a better understanding of what's going on.petrochenkov commentedon Apr 4, 2020
Fixed in #70768.
Rollup merge of rust-lang#70768 - petrochenkov:macambig, r=Centril,ma…