Appreciation to https://github.com/jnthn for his recent update to
https://github.com/jnthn/p6-io-socket-async-ssl.
My lab consists of the below Linux platforms, where the starred four
distributions were snagged on IO::Socket::Async::SSL, thereby holding back cro.
Not tonight!
CentOS
About the documentation in general...
> > that particular pair-input syntax is my least favorite.
> > Flipping around the order of key and value when the value is a numeric...?
> >
> > And it isn't needed to demo the operator, any pair input syntax works.
> > I might argue that examples should
First off, much thanks to Ralph Mellor for his detailed explanations.
Ralph Mellor wrote:
> @r ,= 'd';
>
> The above expands to:
>
> @r = @r , 'd';
Okay, that makes sense. So the circular reference I thought I
was seeing is really there, and it's working as designed.
There isn't anything
I accidentally sent this privately.
-- Forwarded message -
From: Ralph Mellor
Date: Fri, Nov 27, 2020 at 6:06 PM
Subject: Re: The ,= operator
To: William Michels
> I can reproduce your results on Rakudo_2020.10, but I'm afraid I don't
> have much more to say about the ",="
@r ,= 'd';
The above expands to:
@r = @r , 'd';
That in turn passes a list of two values to the LHS receiver.
That receiver is `@r`, an array, and what arrays do with `=`
is to empty themselves and then assign the list of elements
on the RHS of the `=` into corresponding `Scalar`s stored in
Hi Joe,
I can reproduce your results on Rakudo_2020.10, but I'm afraid I don't
have much more to say about the ",=" operator since I'm unfamiliar
with it.
Do the "docs" page(s) make more sense changing the phrase
"class-dependent" behavior to "hash-dependent" behavior?
Best, Bill.
On Thu, Nov
