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 points to CORE.setting, previously it did not (my $x = fail) #5982
Comments
From @AlexDanielCode: Result (2015.12,2016.05): Result (2016.06,HEAD): It is mostly OK, but the previous error message was slightly better because it did not point to “CORE.setting.moarvm line 1” (which brings no useful information). |
From @AlexDanielGolfed to one character. Code: On 2017-01-04 19:04:11, alex.jakimenko@gmail.com wrote:
|
From @zoffixznetm: Backtrace::Frame.^lookup("is-setting").wrap: method () { prolly need something similar for JVM |
From @zoffixznetTests in rakudo/rakudo@53a6d3aff6 |
From @usev6This now works on JVM as well (see rakudo commit c3c86dcf51). The test in t/05-messages/01-errors.t passes. $ ./perl6-j -e 'my $x = fail' I'm closing this ticket as 'resolved'. |
1 similar comment
From @usev6This now works on JVM as well (see rakudo commit c3c86dcf51). The test in t/05-messages/01-errors.t passes. $ ./perl6-j -e 'my $x = fail' I'm closing this ticket as 'resolved'. |
@usev6 - Status changed from 'new' to 'resolved' |
Migrated from rt.perl.org#130509 (status was 'resolved')
Searchable as RT130509$
The text was updated successfully, but these errors were encountered: