You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
IMO that Mu should be a Nil as well, as many routines don't take a Mu and so working with bare Mu is painful. In fact, if you index into that element, you get a Nil instead of a Mu
Also, looks like it doesn't even get hllized in some cases:
<Zoffix_> m: "ac" ~~ /(.)(.)?(.)/; for $/.list { .say }
<camelia> rakudo-moar 0a32c6212: OUTPUT: «「a」Cannot call method 'say' on a null object in block <unit> at <tmp> line 1»
The text was updated successfully, but these errors were encountered:
I disagreed with 2016-Zoffix and threw out that test. It should be placed back (in potentially modified form) to re-cover RT#129299.
# RT #129299
subtest '$/.list returns all items even with optional captures in the middle', {
"ac"~~ /(.)(.)?(.)/;
my ($one, $two, $three) =$/.list;
is$one, 'a', 'first item';
is$two.^name, 'Mu', 'second item'; # can't use is-deeply to test for Mu'sis$three, 'c', 'third item';
}
zoffixznet
changed the title
A hole in $/.list is a Mu, but a hole in @a.List is a Nil
A hole in $/.list is a Mu, but a hole in @a.List is a Nil / null object error
Jul 15, 2018
IMO that
Mu
should be aNil
as well, as many routines don't take aMu
and so working with bareMu
is painful. In fact, if you index into that element, you get aNil
instead of aMu
Also, looks like it doesn't even get hllized in some cases:
The text was updated successfully, but these errors were encountered: