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
Cross meta operator on empty list complains "This type (Scalar) does not support elems" #6289
Comments
From @thundergnatUsing a cross meta operator on an empty list complains "This type say (1,2).elems; say ().elems; say (1,2) X (); yields "20This type (Scalar) does not support elems" Seems to work correctly with arrays instead of lists. say [1,2].elems; say [].elems; say [1,2] X []; Linux Mint 17.2
|
From @zoffixznethttps://irclog.perlgeek.de/perl6/2017-05-29#i_14654174 16:54 bisectable6 MasterDuke, bisect log: https://gist.github.com/7d49ce1401bee0ab3127c5d1be2a919e 16:57 Zoffix m: use nqp; nqp::elems(nqp::getattr((), List, '$!reified')) 17:00 m: use nqp; dd nqp::getattr((), List, '$!reified').^name; dd nqp::getattr([], List, '$!reified').^name |
The RT System itself - Status changed from 'new' to 'open' |
From @lizmat
FWIW, I’m testing a fix. Liz |
From @zoffixznetOn Mon, 29 May 2017 10:02:27 -0700, thundergnat@comcast.net wrote:
Thank you for the report. lizmat++ fixed the issue. Fix: rakudo/rakudo@9494cbd3b9 |
@zoffixznet - Status changed from 'open' to 'resolved' |
From @smlsOn Mon, 29 May 2017 11:36:49 -0700, cpan@zoffix.com wrote:
Re-opening, because it hasn't been fixed for the Xop case yet: ➜ say () X+ (1, 2); ➜ say (1,2) X~ (); ➜ say () X=> (); Bisectable¹ blames a commit² from January. [1] https://gist.github.com/Whateverable/f1b3066f1e2c45df7ab5e0aa7aeee3a7 This is Rakudo version 2017.09-142-ga89add0bf built on MoarVM version 2017.09.1-49-gb3dd812a |
@smls - Status changed from 'resolved' to 'open' |
From @dogbert17On Sat, 30 Sep 2017 12:40:59 -0700, smls75@gmail.com wrote:
Fixed with commit rakudo/rakudo@6c93fde Closing |
@dogbert17 - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#131395 (status was 'resolved')
Searchable as RT131395$
The text was updated successfully, but these errors were encountered: