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
LTA error message when forgetting to close block inside string in Rakudo #4284
Comments
From @drforrReading through S26 it doesn't explicitly state that declarator comments --cut here-- -cut here-- |
From @FROGGSFROGGS: m: say "#={ 42 }" # DrForr: your ticket is invalid So, we'd like to see that a closing curly is expected I think. |
The RT System itself - Status changed from 'new' to 'open' |
From @masakOn Mon Jun 01 01:15:07 2015, FROGGS.de wrote:
Also, as long as we're wishing for ponies and butterflies in the error message: one thing that Perl 5 still does better is to say where the runaway thing *began*, in this case the block. Because it's often a mistake, the programmer may not be aware of which thing it is that is unbalanced. My ideal error message would look something like this: Opening curly without closing curly in string -- did you forget to close the block? |
From @geekosaurOn Mon, Jun 1, 2015 at 3:58 AM, via RT <perl6-bugs-followup@perl.org> wrote:
That's not comments being parsed, it's {...} being an embedded expression -- |
From @AlexDanielhttps://irclog.perlgeek.de/perl6/2017-12-01#i_15520545 On 2015-06-01 04:26:37, masak wrote:
|
From @AlexDanielhttps://irclog.perlgeek.de/perl6/2017-12-02#i_15524141 Marking as 「testneeded」 On 2017-12-01 14:31:15, alex.jakimenko@gmail.com wrote:
|
From @AlexDanielTests here: Raku/roast@2dd5ee1 Resolved. Further discussion on rakudo/rakudo#1475 On 2017-12-02 14:39:07, alex.jakimenko@gmail.com wrote:
|
@AlexDaniel - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#125299 (status was 'resolved')
Searchable as RT125299$
The text was updated successfully, but these errors were encountered: