[perl #132352] Set operators unfriendly to mutable types

[Aleks-Daniel Jakimenko-Aleksejev via RT]

Does it mean that this now needs tests?

On 2017-10-30 06:42:25, elizabeth wrote:
> > On 24 Oct 2017, at 12:56, Zoffix Znet via RT <perl6-bugs-
> > follo...@perl.org> wrote:
> > On Mon, 23 Oct 2017 09:12:58 -0700, sml...@gmail.com wrote:
> >> On Mon, 23 Oct 2017 05:23:55 -0700, c...@zoffix.com wrote:
> >> The "solution", IMO, would not be to make your quoted example work
> >> (by
> >> adding further special cases to the return types of the setty
> >> operators or otherwise), but rather to make the following variation
> >> of
> >> it work:
> >>
> >> my %days is SetHash = Date.today … Date.new: '2014-04-02';
> >>
> >> %days ∖= %days.grep: *.key.day-of-week > 5;
> >>
> >> %days{Date.today}:delete;
> >>
> >> ...and then promote %-sigiled SetHash variables as the recommended
> >> way
> >> to store SetHash'es.
> >>
> >> It should be possible to make this last example work by implementing
> >> `method STORE` for type SetHash, right?
> >>
> >> (That it currently doesn't, may well be an oversight rather than a
> >> design choice.)
>
> Commit b6a4d5b555520451c5c8a made this possible:
>
> my %d is SetHash = Date.today .. Date.new("2017-11-30”);
> %d .= grep: *.key.day-of-week > 5;
> dd %d;
> ================================
>
SetHash.new(Date.new(2017,11,5),Date.new(2017,11,12),Date.new(2017,11,26),Date.new(2017,11,4),Date.new(2017,11,19),Date.new(2017,11,11),Date.new(2017,11,18),Date.new(2017,11,25))