On Mon, Mar 20, 2023 at 10:42:45PM +, Ralph Mellor wrote:
> On Mon, Mar 20, 2023 at 12:49 AM rir wrote:
> >
> > I did, and do, recognize the validity of the problem of 'undefine' not
> > not aligning with '.defined'.
>
> But do you understand the problem I was trying to communicate?
I'm unable to follow the whole thread in depth, but the point I'd like to make
is directly related to the initial example. My question would be: what exactly
do we undefine? I mean, all the discussion about definedness and truthiness is
undoubtedly great, and I mean no pun here. Special thanks
If you made actual evidential arguments why it's good that Nil gets fed
into @variables on assignment, or why is it good that @variables are,
yes, both defined and DEFINITE when only declared, why this
inconsistency, or counterpointing design,with $variables, is a good
thing, we could discuss
I see weaknesses in my attempt to explain Raku's design related to
"definedness".
(I personally think there would best be a documentation page dedicated to the
triumvirate of definiteness, definedness, and truthiness, but here I'm trying to
achieve a balance between being short enough for this
Grr, sorry for the spam. After all this trying, the last part still
couldn't be delivered. So here is the whole message instead:
https://gist.github.com/2colours/53b3c3108b0a44fa559eeed0370c26bf.
it does no good, ever, that you get to store a Nil value ... in an array
Why do you think the `is default(Nil)` idiom for storing `Nil`s in `Scalar`s
is OK except when the `Scalar`s are inside an array?
I grant that, as jnthn put it in an SO discussing this:
While there is the `is
(Since this mail couldn't be delivered at first, I'll try to
aggressively split it this time...)
Dear Ralph,
I'm sorry that you get frustrated but this is still for all intents and
purposes a technical discussion so I don't think it does any good to be
vocal about it. There are good points
