On Sat, 21 Nov 2015 06:48:27 -0800, timo wrote:
> Reproducing test:
>
> my @a[3;3] = , , ; say @a; # works
> my Str @a[3;3] = , , ; say @a; # fails
>
> 153852 jnthn │ m: say ((0 xx 10) xx 10).WHAT
> 153852 +camelia │ rakudo-moar : OUTPUT«(List)»
> 153857 jnthn │ Curious...
> 153933 tim
On Sat, 07 May 2016 13:26:09 -0700, sml...@gmail.com wrote:
> Confirmed on current Rakudo.
>
> Interestingly, it works if `for @a` is replaced with `for @a[*]`:
>
> ➜ my Int @a; @a[5] = 42; $_ = 100 for @a[*]; say @a;
> [100 100 100 100 100 100]
Seems to have been fixed with Rakudo
Just to clarify, the last snippet now produces 0 0 0 0, which is indeed
correct.
There are tests for this change in general, but possibly not for that
particular case. Can we get it covered just in case?
｢testneeded｣
On 2018-02-06 05:51:23, jan-olof.hen...@bredband.net wrote:
> On Sun, 28 Aug 20
On Sun, 28 Aug 2016 02:56:47 -0700, sml...@gmail.com wrote:
> This is how a state variable normally works:
>
> ➜ for ^2 { for ^2 { say (state $a)++ } }
> 0
> 1
> 0
> 1
>
> But when it is declared inside a {} interpolation in a string, it
> misbehaves:
>
> ➜ for ^2 { for ^2 { say "{ (state $a)+
