# New Ticket Created by  "Carl Mäsak" 
# Please include the string:  [perl #123176]
# in the subject line of all future correspondence about this issue. 
# <URL: https://rt.perl.org/Ticket/Display.html?id=123176 >


<Mouq> m: -> $a = 0 { $a }
<camelia> rakudo-moar 41fe4f: OUTPUT«===SORRY!=== Error while
compiling /tmp/Xy5Szv397I␤Unexpected block in infix position (two
terms in a row, or previous statement missing semicolon?)␤at
/tmp/Xy5Szv397I:1␤------> -> $a = 0 ⏏{ $a }␤    …»
<masak> Mouq: huh.
<Mouq> m: 0 { 42 }
<camelia> rakudo-moar 41fe4f: OUTPUT«===SORRY!=== Error while
compiling /tmp/_b8MbmIQZD␤Unexpected block in infix position (two
terms in a row, or previous statement missing semicolon?)␤at
/tmp/_b8MbmIQZD:1␤------> 0 ⏏{ 42 }␤    expecting any of:…»
<masak> feels like the '{' is not acting properly as a stopper for the EXPR
<jnthn> I don't even know if we make it that far.
<jnthn> As in, I think the error might happen while parsing the
default for the arg
<TimToady> ->'s sig is supposed to have a terminator of \s{
* masak submits rakudobug
<TimToady> std: -> $a = 0 { $a }
-!- camelia [came...@ns1.niner.name] has quit [Quit: camelia]
<TimToady> ooopsss
<Mouq> TimToady: STD has the same error
<jnthn> Mouq: Ah, I'll stop playing "spot the STD discrepancy" then ;)
<TimToady> oh, wait, the \s{ terminator is on xblocks, not here (yet)
<jnthn> TimToady: Hacky fix may be that infix:sym<lambda> needs to be
attentive to the current precedence limit we're parsing under

Reply via email to