On Sat, Mar 18, 2023 at 6:28 PM Polgár Márton
wrote:
>
> For what it's worth, I think most of these behaviors that sometimes
> even contradict each other (like the "freshly undefined" array being
> both .defined and .DEFINITE) are just design mistakes from a different time.
There are no mistakes
On Mon, Mar 20, 2023 at 10:42 PM Ralph Mellor wrote:
>
> * Definiteness or definedness? If you want it indefinite (or undefined),
> call `.WHAT` on the argument.
That should be "Bind the result of `.WHAT` called on the argument".
Similarly:
> * Truthiness? Want a fresh false instance? Call `.ne
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?
What you're writing suggests to me you know some other PL(s) that
have notions of
Marton, I like the practicality of your advice to preferring scalar
containers.
Do you think 'undefine' should go away in 6.e with only the proposed
replacements?
Marton wrote:
> quickly messing things up to test this out but since we were talking about a
> "scheduled bug" anyway, I think that co
