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.
It was never "the right thing" that you cannot reasonably indicate for
an array
On Fri, Mar 17, 2023 at 11:11 PM rir wrote:
>
> Deprecating 'undefine' is just making something easy more difficult.
I see a problem with `undefine`:
```
my @bar;
say @bar.defined, @bar.DEFINITE; # TrueTrue
undefine @bar;
say @bar.defined, @bar.DEFINITE; # TrueTrue
```
I think a warning about
