Hi Yary,
I went over this with Joe as well, and I was equally confused. So if I
understand what you're saying correctly, if we see something like
"Bool :$match" that says we should drop the dollar-sign ($) and enter
":match" to set "Bool" = True, and thus return the list of match
objects?
On anot
Hello,
I have a question related to the 'colon syntax' of Raku, which allows
you to call methods without parenthesis like this:
class Foo
{
method print($x, $y)
{
say "bar: {$x}, {$y}"
}
}
my $a = Foo.new;
$a.print: 3, 5; # ...this is what
Hi Bill,
In your repl examples you're actually passing the True or False as a
positional parameter, which makes it go into the slot for $limit, not
the slot for :$match.
In order to pass true or false for the "match" named parameter you have
different syntactical options:
comb(/\w/, "a;b;c", m
Hi,
I'm sending an email rather than IRC to catch more feedback.
There are several CompUnit::Repository classes, viz.
AbsolutePath
FileSystem
Installable
Installation
Locally
NQP
Perl5
Spec
Unknown
Would it be possible for someone to provide a line or two as to the
purpose/use/use-ca
Hello Timo, and thank you for taking the time to explain how "comb"
routine signatures work. I have no doubt your description is the
correct way to use comb routine(s) in Raku/Perl6.
First of all, I should preface my remarks by saying that I'm using
Rakudo (moar) 2019.07.1, with the Linenoise modu
Oh dang!
This may very well be a rakudobug. I've actually never used the sub form
of comb, only ever the method form, for which the "match" named
parameter definitely exists:
"a;b;c".comb(/\w/, match => True);
(「a」 「b」 「c」)
Someone will have to fix that and then the code from my mail will
retroa
I think
https://github.com/rakudo/rakudo/commit/dd2f072d6aae04bfcf2603c6bdcd2f2e7d804ea8
fixed it.
> On 16 Nov 2019, at 18:57, Timo Paulssen wrote:
>
> Oh dang!
>
> This may very well be a rakudobug. I've actually never used the sub form
> of comb, only ever the method form, for which the "ma
William Michels wrote:
> I went over this with Joe as well, and I was
> equally confused.
Part of our trouble was we were playing around with the
routine form of comb (rather than the Str method), which
had a bug in it with the :match option (which lizmat just fixed).
Even when we tried the Righ