Hi Larry,
I have a follow up question based on your May 31 email that I'm hoping
you may be able to answer. In that email, you wrote:
> In my opinion, the most consistent approach is to disallow any
> autothreading of the argument to .ACCEPTS, such that
> 3.ACCEPTS(any(3,4)) simply returns False
Hi Larry,
I have a follow up question based on your May 31 email that I'm hoping
you may be able to answer. In that email, you wrote:
> In my opinion, the most consistent approach is to disallow any
> autothreading of the argument to .ACCEPTS, such that
> 3.ACCEPTS(any(3,4)) simply returns False
On Thu, Nov 4, 2021 at 7:27 PM Joseph Brenner wrote:
>
> Yes, thanks, I'd managed to forget that we had a go-round
OK. Cool. I wasn't sure if it was the same issue (hence my aiui
qualification). It's helpful to hear confirmation you consider this
to be the same issue.
Btw, I'd say it was not onl
If this pull request is merged:
https://github.com/rakudo/rakudo/pull/4620
you will get a deprecation notice at the end of your program of the locations
in your code that need changing.
Liz
> On 5 Nov 2021, at 19:54, Joseph Brenner wrote:
>
> Yes, this feels like natural Raku code to a lo
Yes, this feels like natural Raku code to a lot of us:
given any( $o1, $o2 ) { when { ... } }
If there's some rule like, "don't use junctions
on the left hand side of a smartmatch" that
hasn't been made clear, and there's certainly no
roast tests that check this, so consequently the
behavior
and I realize that what I just typed doesn't help a whole lot, what if you
have a junction of things and you want to tell if any/one/all/none
smartmatch the same thing... OK..
-y
On Thu, Nov 4, 2021 at 6:38 PM yary wrote:
> Something that helps me reason about this is thinking of how regular
>
Something that helps me reason about this is thinking of how regular
expressions match against strings, to remember that which goes on which
side is important...
> "this has a Q in it" ~~ / 'Q' / # of course this works
｢Q｣
> / 'Q' / ~~ "this has a Q in it" # of course this breaks
Regex object
> ... we'd need to go
> through detailed, calm, measured discussion if we're to minimize
> the pain it seems we'll inevitably endure pain to dig ourselves out
> of the hole we'd be in.
Yes, this could be a bad one.
Yes, thanks, I'd managed to forget that we had a go-round on this one
six months ago, even though that one came out of the Raku Study Group
I run.
I'm actually finding this one profoundly depressing, but I probably
shouldn't get into it. My thoughts are running along lines like "how
is it possibl
On Thu, Nov 4, 2021 at 6:34 PM Ralph Mellor wrote:
>
> Aiui, until we listen to Larry, accept he's right, and fix Rakudo,
> the results when the topic of a smart match is a Junction will
> randomly depend on which version of Rakudo you're using.
Further, aiui, when we do, there may be a world of
Aiui, we discussed this issue in May and Larry explained
that this would happen.
Larry doesn't speak up much, and I realized a few months
later that it seemed no one had done anything about what
he had said. So I filed an issue:
https://github.com/Raku/problem-solving/issues/297
Aiui, until we l
I see the same as Joseph:
$ raku
Welcome to 𝐑𝐚𝐤𝐮𝐝𝐨™ v2021.06.
Implementing the 𝐑𝐚𝐤𝐮™ programming language v6.d.
Built on MoarVM version 2021.06.
To exit type 'exit' or '^D'
> say do given all(3,7) { when Int { "both are Int" }; default {"not
similar"} };
not similar
> say so do all(3,7) ~~ Int;
Joseph Brenner wrote:
> Andy Bach wrote:
>> Joseph Brenner wrote:
>>> I'd thought that that [this] would confirm that both elements were Int:
>>> say do given all(3,7) { when Int { "both are Int" }; default {"not
>>> similar"} };
>>> ## not similar
>> I get a different result
>> $ raku
That's interesting. I just re-built from github and I'm still
seeing the behavior I reported:
raku -e 'say do given all(3,7) { when Int { "both are Int" };
default {"not similar"} };'
not similar
That's with:
raku --version
Welcome to Rakudo™ v2021.10-43-ga8329f6fd.
Implementing the R
> I'd thought that that would confirm that both elements were Int:
say do given all(3,7) { when Int { "both are Int" }; default {"not similar"}
};
## not similar
I get a different result
$ raku -e ' say do given all(3,7) { when Int { "both are Int" }; default
{"not similar"} };'
both are I
15 matches
Mail list logo
