You'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). I don't know if there are docs on that topic anywhere. I mentioned it in the squashathon guide (https://github.com/rakudo/rakudo/wiki/Rakudo-SQUASHathon-Guide#resolving-testneeded-tickets) but we probably need a proper explanation somewhere.
On 2017-10-21 11:54:34, allber...@gmail.com wrote: > On Sat, Oct 21, 2017 at 12:12 PM, Brad Gilbert via RT < > perl6-bugs-follo...@perl.org> wrote: > > > On Sat, 21 Oct 2017 08:18:46 -0700, alex.jakime...@gmail.com wrote: > > > https://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. > > > > > > > I don't think we should force all future implementations to add BUILDALL. > > > > Being listed in the methods does not mean part of the spec. I mean, if it > did then .^methods wouldn't be allowed to show user added methods either. > Or did you mean something else here? in which case you need to explain it > better. >
