pugscommitbot, channeling Larry (>):
> [...]
> + $x = "Today" but Tue; # $x.Day is read-only
> + $x = "Today" but Day; # $x.Day is read-write
> +
> +Mixing in a specific enum object implies only the readonly accessor.
> +
> $x = "Today" but Tue;
>
> -really means something more like:
> +really means something like:
>
> - $x = "Today";
> - $x does Has[Day, '$.Day', (:rw), { Tue }];
> + $x = "Today".clone;
> + $x does anon role { method Day { Day::Tue } };
> [...]
I'm not 100% clear on when this 'anon' keyword is to be applied and when not.
Why is it 'anon role' for anonymous roles but not 'anon enum' for
anonymous enumerations?
If 'anon' isn't strictly required before 'enum', is it still allowed?
// Carl
