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
error message talks about ~ but there is no ~ in my code (33..126 .pick.chr) #4795
Comments
From @AlexDanielCode: Result: Actually thrown at: The solution is to put parens: But the error message is not even close to helping with that. The biggest |
From @timoThis error occurs because 126.pick gives 126, 126.chr is " So this is just a precedence problem with ranges. Do you have a better suggestion for the error message here? Otherwise |
The RT System itself - Status changed from 'new' to 'open' |
From @AlexDanielThanks! Indeed! I should have tried understanding the issue and golfing it So the snippet can be golfed down to: The bug is still there, please don't close. In fact, the title is very “126.chr” is still “126.chr”. It is less than awesome to whine about some Awesome error message should go like this: On Sat, Nov 28, 2015 at 7:29 PM, Timo Paulssen via RT <
|
From @AlexDanielAs far as I know, this ticket is impossible to resolve. At least not with what we have now in rakudo. To produce an error message that is more precise we'll need more information than just a line number, but we don't have that during the run time. See https://rt-archive.perl.org/perl6/Ticket/Display.html?id=128402 Maybe once RT #128402 is resolved there will be something we could use for that ticket… On 2015-11-28 11:25:00, alex.jakimenko@gmail.com wrote:
|
From @smlsOn Wed, 04 Oct 2017 22:10:22 -0700, alex.jakimenko@gmail.com wrote:
Couldn't the confusing wording be fixed without additional information? As I understand it, the problem with the current message is that the in '⏏~' (indicated by ⏏) part leads people to think it's referring to a position in the source code, when it is actually referring to a position in a string. Especially because the "in block ... in file ... at line ..." line comes directly after it. |
From @AlexDaniel“Couldn't the confusing wording be fixed without additional information?” Yes. But how? We can't *remove* this hint because sometimes it is super useful. On 2017-10-06 11:13:34, smls75@gmail.com wrote:
|
From @geekosaurIs it possible to signal to the error handler that it is talking about a On Sat, Oct 7, 2017 at 5:18 PM, Aleks-Daniel Jakimenko-Aleksejev via RT <
-- |
Migrated from rt.perl.org#126757 (status was 'open')
Searchable as RT126757$
The text was updated successfully, but these errors were encountered: