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
Dead code in HyperWhatever, 「.new」 is not supposed to work but it does (HyperWhatever.new) #5551
Comments
From @AlexDanielLet's look at the code in Rakudo! From src/core/Whatever.pm my class HyperWhatever { So it seems like it should throw a warning if we try to create a HyperWhatever object, right? Let's see! Code: Result: Apparently, the code in “.new” method of Whatever.pm is not being reached. |
From @zoffixznetOn Tue Aug 09 15:25:11 2016, alex.jakimenko@gmail.com wrote:
Bizarrely, SourceBaby points to the right place, so I don't get why it doesn't work: https://github.com/rakudo/rakudo/blob/c587b9d/src/core/Whatever.pm#L10 I tried copying that little bit into a test file and rename the class to HyperWhatever2 and invoke the new and then it throws fine. |
The RT System itself - Status changed from 'new' to 'open' |
From @zoffixznetOn Tue, 09 Aug 2016 15:25:11 -0700, alex.jakimenko@gmail.com wrote:
Dug a bit more into it... It's getting interpreted as an attempt to hyper-whatever a .new call (so like **.new), and the QAST gets added a call to &HYPERWHATEVER, which returns the sub you see in the output. No idea if there's any easy way to make it DTRT, so I'm going to leave this for someone else... |
From @zoffixznetOn Tue, 09 Aug 2016 15:25:11 -0700, alex.jakimenko@gmail.com wrote:
Thank you for the report. This is now fixed. Fix: rakudo/rakudo@57a1aa7a87 On Thu, 11 Aug 2016 20:41:53 -0700, cpan@zoffix.com wrote:
On Sun, 18 Dec 2016 13:18:36 -0800, cpan@zoffix.com wrote:
It's OK, 2016-Zoffix. I got your back, bruh. |
@zoffixznet - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#128880 (status was 'resolved')
Searchable as RT128880$
The text was updated successfully, but these errors were encountered: