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
BUILDALL is listed as one of the methods, maybe that's not right (say $foo.^methods) #6602
Comments
From @AlexDanielCode: ¦«2015.12»: ¦«2016.06»: ¦«2016.12»: ¦«2017.06»: ¦«f72be0f130cf»: Bisectable points at two relevant commits: I don't know if BUILDALL should be listed or not. My gut feeling says that it shouldn't be, but feel free to argue otherwise. I'm just the messenger. |
From @lizmat
Well, it *is* an auto-generated method that is installed in the namespace. Just like “bar”. So either we should show both, or neither. Or introduce a flag to include/exclude auto-generated methods. But then we would need to mark those methods as auto-generated somehow. |
The RT System itself - Status changed from 'new' to 'open' |
From @AlexDanielhttps://irclog.perlgeek.de/perl6-dev/2017-10-21#i_15334639 I' think we should test that both are listed, and we can close the ticket. On 2017-10-13 04:50:32, elizabeth wrote:
|
From @b2gillsOn Sat, 21 Oct 2017 08:18:46 -0700, alex.jakimenko@gmail.com wrote:
I don't think we should force all future implementations to add BUILDALL.
I think BUILDALL is different than bar for several reasons, (I mean that 「has $.bar」 as an implicit declaration So I think discussing whether this use of BUILDALL needs to be hidden can be |
From @AlexDaniel“I don't think we should force all future implementations to add BUILDALL.” Not sure what this remark is for. Can be rakudo tests. On 2017-10-21 09:12:32, brad wrote:
|
From @geekosaurOn Sat, Oct 21, 2017 at 12:12 PM, Brad Gilbert via RT <
Being listed in the methods does not mean part of the spec. I mean, if it -- |
From @AlexDanielYou're right, sorry, I should've been more clear. Tickets are not closed without tests, but as you pointed out not everything should be spec-ed. That's correct. Therefore, some tests go to https://github.com/rakudo/rakudo/tree/nom/t (these tests can be changed at any moment and don't serve as a guarantee for anything, they exist merely to keep rakudo from regressing). On 2017-10-21 11:54:34, allbery.b@gmail.com wrote:
|
From @zoffixznetTests: rakudo/rakudo@20d67a3d4d |
@zoffixznet - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#132283 (status was 'resolved')
Searchable as RT132283$
The text was updated successfully, but these errors were encountered: