[perl6/specs] baec19: Update S27-perl-culture-draft.pod6

2017-08-26 Thread GitHub
Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: baec197a059726524d2071062cb29176778a2ae9 https://github.com/perl6/specs/commit/baec197a059726524d2071062cb29176778a2ae9 Author: Xliff Date: 2017-08-24 (Thu, 24 Aug 2017) Changed

[perl #131964] Regex anchors ^, ^^, $ and $$ confused in

2017-08-26 Thread via RT
# New Ticket Created by Moritz Lenz # Please include the string: [perl #131964] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=131964 > This is Rakudo version 2017.08-11-g6cec6b7 built on MoarVM version 2017.08.1-19-g151a256

Re: [perl #131965] Shaped arrays can't have zero size

2017-08-26 Thread Brandon Allbery via RT
> Well, what do you mean? Of course you can't put anything into it, and any > attempt to index it will throw. It may seem useless, however, if you can > have > an empty array, why can't you have a shaped empty array? > Only if all dimensions are unindexable. Otherwise you have something with

Re: [perl #131965] Shaped arrays can't have zero size

2017-08-26 Thread Brandon Allbery
> Well, what do you mean? Of course you can't put anything into it, and any > attempt to index it will throw. It may seem useless, however, if you can > have > an empty array, why can't you have a shaped empty array? > Only if all dimensions are unindexable. Otherwise you have something with

[perl #131965] Shaped arrays can't have zero size

2017-08-26 Thread Aleks-Daniel Jakimenko-Aleksejev via RT
Well, what do you mean? Of course you can't put anything into it, and any attempt to index it will throw. It may seem useless, however, if you can have an empty array, why can't you have a shaped empty array? On 2017-08-26 17:13:02, allber...@gmail.com wrote: > How exactly do you index such an

Re: [perl #131965] Shaped arrays can't have zero size

2017-08-26 Thread Brandon Allbery
How exactly do you index such an array? On Sat, Aug 26, 2017 at 8:11 PM, Aleks-Daniel Jakimenko-Aleksejev via RT < perl6-bugs-follo...@perl.org> wrote: > Indeed. The limit was introduced as a response to this ticket: > https://rt.perl.org/Ticket/Display.html?id=126800 > The check is probably too

Re: [perl #131965] Shaped arrays can't have zero size

2017-08-26 Thread Brandon Allbery via RT
How exactly do you index such an array? On Sat, Aug 26, 2017 at 8:11 PM, Aleks-Daniel Jakimenko-Aleksejev via RT < perl6-bugs-follo...@perl.org> wrote: > Indeed. The limit was introduced as a response to this ticket: > https://rt.perl.org/Ticket/Display.html?id=126800 > The check is probably too

[perl #131965] Shaped arrays can't have zero size

2017-08-26 Thread Aleks-Daniel Jakimenko-Aleksejev via RT
Indeed. The limit was introduced as a response to this ticket: https://rt.perl.org/Ticket/Display.html?id=126800 The check is probably too aggressive, and indeed, maybe there's nothing wrong with 0 sized arrays. I wonder what was the justification for making the check inclusive. On 2017-08-26

[perl #131966] Shaped native arrays with negative sizes (my int @a[-9999999999999999])

2017-08-26 Thread via RT
# New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev # Please include the string: [perl #131966] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=131966 > Code: my int @x[-2**63]; say +@x Result: -9223372036854775808 See

[perl #131965] Shaped arrays can't have zero size

2017-08-26 Thread via RT
# New Ticket Created by David Warring # Please include the string: [perl #131965] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=131965 > This is OK: % perl6 -e'my $size = 2; my @xref[$size,3] = ([1,2,3], [4,5,6]); say

[perl #129845] [TESTNEEDED] [CONC] `.dir` returns corrupted `IO::Path`s under concurrent load

2017-08-26 Thread Aleks-Daniel Jakimenko-Aleksejev via RT
It is more or less reliable actually. I think writing a stresstest will do. On 2017-08-26 05:33:17, sml...@gmail.com wrote: > Both the demo script (from the top post) and the one-line test case > (2nd post) now pass without error! > > Bisectable identifies a commit from last week as the fix: > >

[perl #130604] [PARSER] Weirdness when mixing `..` and `...` without parens

2017-08-26 Thread Aleks-Daniel Jakimenko-Aleksejev via RT
Indeed, I'm not sure what I was smoking. On 2017-01-20 21:27:50, sml...@gmail.com wrote: > > It numifies ranges so that the number of elements is used. In other > > words, 1..2 > > works like 2 and 1..1 works like 1. > > No, if it worked like that then the first two examples would throw the > same

Re: [perl #131962] [REGRESSION] `Pair.kv`/`.keys`/.`values` dies if either the key or the value is `Mu`

2017-08-26 Thread Elizabeth Mattijsen
Fixed with a5014fd0855545cc083b3590 , tests needed. > On 26 Aug 2017, at 13:10, Sam S. (via RT) > wrote: > > # New Ticket Created by Sam S. > # Please include the string: [perl #131962] > # in the subject line of all future correspondence about this issue. > #

Re: [perl #131962] [REGRESSION] `Pair.kv`/`.keys`/.`values` dies if either the key or the value is `Mu`

2017-08-26 Thread Elizabeth Mattijsen via RT
Fixed with a5014fd0855545cc083b3590 , tests needed. > On 26 Aug 2017, at 13:10, Sam S. (via RT) > wrote: > > # New Ticket Created by Sam S. > # Please include the string: [perl #131962] > # in the subject line of all future correspondence about this issue. > #

[perl #129845] [CONC] `.dir` returns corrupted `IO::Path`s under concurrent load

2017-08-26 Thread Sam S. via RT
Both the demo script (from the top post) and the one-line test case (2nd post) now pass without error! Bisectable identifies a commit from last week as the fix: https://gist.github.com/97d96022fdfed416e67ecadf5b2b9353 https://github.com/rakudo/rakudo/commit/231cb3f Is there a way to

[perl #130773] [BUG] Bogus "Useless use" warning for WhateverCode in EVAL

2017-08-26 Thread Sam S. via RT
This bug is still present in Rakudo version 2017.08-8-g753c9a5ea built on MoarVM version 2017.08.1-19-g151a2563 implementing Perl 6.c.

[perl #130711] [REGEX] `**` quantifier with dynamic count, misbehaves under `:exhaustive` matching

2017-08-26 Thread Sam S. via RT
This bug is still present in Rakudo version 2017.08-8-g753c9a5ea built on MoarVM version 2017.08.1-19-g151a2563 implementing Perl 6.c.

[perl #130602] [BUG] `1, 2 Xand "ab".ords` fails with "Cannot invoke this object (REPR: Uninstantiable; Callable)"

2017-08-26 Thread Sam S. via RT
This bug is still present in Rakudo version 2017.08-8-g753c9a5ea built on MoarVM version 2017.08.1-19-g151a2563 implementing Perl 6.c.

[perl #130572] Parenthesized `for` loop is eager, even with `lazy` keyword

2017-08-26 Thread Sam S. via RT
This bug is still present in Rakudo version 2017.08-8-g753c9a5ea built on MoarVM version 2017.08.1-19-g151a2563 implementing Perl 6.c.

[perl #130604] [PARSER] Weirdness when mixing `..` and `...` without parens

2017-08-26 Thread Sam S. via RT
This bug is still present in Rakudo version 2017.08-8-g753c9a5ea built on MoarVM version 2017.08.1-19-g151a2563 implementing Perl 6.c.

[perl #131962] [REGRESSION] `Pair.kv`/`.keys`/.`values` dies if either the key or the value is `Mu`

2017-08-26 Thread via RT
# New Ticket Created by Sam S. # Please include the string: [perl #131962] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=131962 > ➜ say (4 => Mu).kv; Type check failed in binding to parameter 'val2'; expected

Re: [perl #126951] [BUG] Interpolating a typed hash into an argument list produces wrong keys

2017-08-26 Thread Elizabeth Mattijsen
Fixed with 6cec6b7218650aff1780a4dd , tests needed > On 26 Aug 2017, at 10:35, Sam S. via RT wrote: > > Shorter test-case: > >➜ say :{ a => 1, b => 2 }.FLATTENABLE_HASH; >{Str|a => a => 1, Str|b => b => 2} > > Compare to a normal Hash which works fine: >

Re: [perl #126951] [BUG] Interpolating a typed hash into an argument list produces wrong keys

2017-08-26 Thread Elizabeth Mattijsen via RT
Fixed with 6cec6b7218650aff1780a4dd , tests needed > On 26 Aug 2017, at 10:35, Sam S. via RT wrote: > > Shorter test-case: > >➜ say :{ a => 1, b => 2 }.FLATTENABLE_HASH; >{Str|a => a => 1, Str|b => b => 2} > > Compare to a normal Hash which works fine: >

[perl #126951] [BUG] Interpolating a typed hash into an argument list produces wrong keys

2017-08-26 Thread Sam S. via RT
Shorter test-case: ➜ say :{ a => 1, b => 2 }.FLATTENABLE_HASH; {Str|a => a => 1, Str|b => b => 2} Compare to a normal Hash which works fine: ➜ say { a => 1, b => 2 }.FLATTENABLE_HASH; {a => 1, b => 2}

[perl #126951] [BUG] Interpolating a typed hash into an argument list produces wrong keys

2017-08-26 Thread Sam S. via RT
This bug is still present in Rakudo version 2017.08-8-g753c9a5ea built on MoarVM version 2017.08.1-19-g151a2563 implementing Perl 6.c.

Re: User defined infix operators and whitespace

2017-08-26 Thread Norman Gaywood
It seems to work without spaces if you choose a symbol that is not letter-like. # U+1F3B2 Game Die sub infix:<> ( Int $num, Int $size ) { [+] (1..$size).roll($num) }; sub prefix:<> ( Int $size ) { 1$size } say 10; say 46; # ⛏ U+26CF Pick sub infix:<⛏> ( Int $num, Int $size ) { [+]