-
Notifications
You must be signed in to change notification settings - Fork 1
"..." produces a low-level backtrace; running code from file and with -e is different #4435
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
Comments
From @AlexDanielCode: Result: It seems like I should not see that backtrace. There is no such problem But it goes even further: Actually thrown at: As you can see, no stacktrace when running it with -e. However, the same jnthn and moritz discussed that problem a little bit, check out IRC log: |
@coke - Status changed from 'new' to 'open' |
From @cokeOn Fri Jul 24 11:26:41 2015, alex.jakimenko@gmail.com wrote:
This no longer behaves differently in a file version on the command line, both giving: Useless use of constant integer 1 in sink context (line 1) Marking test needed. -- |
From @zoffixznetTests added in Raku/roast@7414702357 |
@zoffixznet - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#125680 (status was 'resolved')
Searchable as RT125680$
The text was updated successfully, but these errors were encountered: