Hi Aleks,
Thanks for reminder i totally forgot about this RT.
Looks like it was fine in 2015
https://github.com/teodozjan/lacuna-cookbuk/commit/f2ebae3efda06f35b1d679e17e14c259bd718b95#diff-73e69e63f060cafc548379f4dcc52105
shall i test it to be 100% sure or you want to close it?
On Sun, Dec 3, 2
Hi Aleks,
Thanks for reminder i totally forgot about this RT.
Looks like it was fine in 2015
https://github.com/teodozjan/lacuna-cookbuk/commit/f2ebae3efda06f35b1d679e17e14c259bd718b95#diff-73e69e63f060cafc548379f4dcc52105
shall i test it to be 100% sure or you want to close it?
On Sun, Dec 3, 2
The problem with let/temp for this situation has been fixed with
752299767bac3c49 . And tests are needed for that.
However, the underlying issue is that the default value of container
descriptors created automatically with “no strict” are Mu rather than Any.
This will need some deeper research
The problem with let/temp for this situation has been fixed with
752299767bac3c49 . And tests are needed for that.
However, the underlying issue is that the default value of container
descriptors created automatically with “no strict” are Mu rather than Any.
This will need some deeper research
Properly fixed with e5b49ce , tests needed for container type / default value
of auto-defined
variables.
> On 3 Dec 2017, at 04:45, Aleks-Daniel Jakimenko-Aleksejev via RT
> wrote:
>
> Still reproducible (2017.11,HEAD(e5b660e))
>
> On 2015-06-13 05:48:13, ronaldxs wrote:
>> From irc
>>
>> ht
Properly fixed with e5b49ce , tests needed for container type / default value
of auto-defined
variables.
> On 3 Dec 2017, at 04:45, Aleks-Daniel Jakimenko-Aleksejev via RT
> wrote:
>
> Still reproducible (2017.11,HEAD(e5b660e))
>
> On 2015-06-13 05:48:13, ronaldxs wrote:
>> From irc
>>
>> ht
Some *able info, if anyone is interested:
Output on all releases:
https://gist.github.com/a68b094519839b939f8c70d66a80d8c0
Some possibly relevant commits:
https://github.com/rakudo/rakudo/commit/92bd7e4f54a92fa660f99b4d056d33a08fb98bd2
https://github.com/rakudo/rakudo/commit/6dae179a8418bd2fcf5cc
FWIW it never worked:
https://gist.github.com/Whateverable/d9dbebb0e985a3964845df2c8652cbdf
On 2017-11-27 17:36:22, comdog wrote:
> I previously asked about this unexpected Z behavior on Stackoverflow
> ( https://stackoverflow.com/q/45001820/2766176 ).
>
> I expected this to change several hash ke