[perl #130970] [BUG] Set.new confused by Nil

2017-09-05 Thread Brian S. Julin via RT
On Tue, 05 Sep 2017 03:21:07 -0700, zef...@fysh.org wrote: > Brian S. Julin via RT wrote: > >It is that Nil is also semantically special as a RHS of an assignment > >or as a parameter. > ... > >This is mentioned in S02. > > Some of the specialness mentioned in S02 doesn't happen, such as .ACCEPTS

[perl #132030] [REGRESSION] Broken Text::CSV tests and possibly other ecosystem fallout

2017-09-05 Thread Aleks-Daniel Jakimenko-Aleksejev via RT
“Will leave this ticket open a little longer for further comments/discussion, but my intention is to reject it.” Nope, that's not exactly a good sounding plan. We'll run toaster and fix all modules that require fixing (or create appropriate issues if fixing something turns out to be too hard). Th

Re: [perl #132035] AutoReply: [LTA] temp on an undeclared dynamic variable produces a not very helpful error

2017-09-05 Thread Brandon Allbery via RT
Or maybe it's not that tricky after all; seems the Failure is actually a useful one (X::Dynamic:NotFound), so introspection of the Failure would reveal the issue. -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com b

Re: [perl #132035] AutoReply: [LTA] temp on an undeclared dynamic variable produces a not very helpful error

2017-09-05 Thread Brandon Allbery
Or maybe it's not that tricky after all; seems the Failure is actually a useful one (X::Dynamic:NotFound), so introspection of the Failure would reveal the issue. -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com b

[perl #132035] [LTA] temp on an undeclared dynamic variable produces a not very helpful error

2017-09-05 Thread via RT
# New Ticket Created by Brandon Allbery # Please include the string: [perl #132035] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=132035 > Seen in IRC: [05 17:51:12] m: grammar { token TOP { :my $*v = 42; }; token foo { {d

[perl #132014] [REGEX] Some Zero-Width assertion appear to not work in

2017-09-05 Thread Sam S. via RT
Duplicate of https://rt.perl.org/Ticket/Display.html?id=131964 ?

Re: [perl #132030] [REGRESSION] Broken Text::CSV tests and possibly other ecosystem fallout

2017-09-05 Thread Brandon Allbery via RT
On Tue, Sep 5, 2017 at 5:40 AM, jn...@jnthn.net via RT < perl6-bugs-follo...@perl.org> wrote: > Failing to close output handles has been clearly documented (and yes, > documented well before the recent buffering change) as something that can > cause data loss. Default output buffering just makes i

Re: [perl #132030] [REGRESSION] Broken Text::CSV tests and possibly other ecosystem fallout

2017-09-05 Thread Brandon Allbery
On Tue, Sep 5, 2017 at 5:40 AM, jn...@jnthn.net via RT < perl6-bugs-follo...@perl.org> wrote: > Failing to close output handles has been clearly documented (and yes, > documented well before the recent buffering change) as something that can > cause data loss. Default output buffering just makes i

Re: [perl #132029] Floppage of atomic tests

2017-09-05 Thread Elizabeth Mattijsen via RT
FWIW, I couldn’t get this to fail on my MBP *while* running make spectest with TEST_JOBS=8 Perhaps this is OS / CPU / compiler dependent? > On 5 Sep 2017, at 09:17, Aleks-Daniel Jakimenko-Aleksejev via RT > wrote: > > Oh. A crude way to reproduce it is: > > while :; do clear; PERL6LIB=lib ./

Re: [perl #132029] Floppage of atomic tests

2017-09-05 Thread Elizabeth Mattijsen
FWIW, I couldn’t get this to fail on my MBP *while* running make spectest with TEST_JOBS=8 Perhaps this is OS / CPU / compiler dependent? > On 5 Sep 2017, at 09:17, Aleks-Daniel Jakimenko-Aleksejev via RT > wrote: > > Oh. A crude way to reproduce it is: > > while :; do clear; PERL6LIB=lib ./

[perl #132034] Presence of NEXT phasers interferes with labeled `next`

2017-09-05 Thread via RT
# New Ticket Created by Zoffix Znet # Please include the string: [perl #132034] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=132034 > https://irclog.perlgeek.de/perl6/2017-09-05#i_15118347 13:17 m: FOO: for 1 { ne

[perl #132030] [REGRESSION] Broken Text::CSV tests and possibly other ecosystem fallout

2017-09-05 Thread jn...@jnthn.net via RT
On Tue, 05 Sep 2017 05:29:00 -0700, 1parr...@gmail.com wrote: > Perl 5 programmers are used to being casual about closing file > handles. Obviously, 6 requires a change of habits. A cultural shift, > if that's not too pretentious a term. Perhaps it needs to be mentioned > in large, friendly letters

[perl #132030] [REGRESSION] Broken Text::CSV tests and possibly other ecosystem fallout

2017-09-05 Thread jn...@jnthn.net via RT
On Tue, 05 Sep 2017 05:29:00 -0700, 1parr...@gmail.com wrote: > Perl 5 programmers are used to being casual about closing file > handles. Obviously, 6 requires a change of habits. A cultural shift, > if that's not too pretentious a term. Perhaps it needs to be mentioned > in large, friendly letters

Re: [perl #132030] [REGRESSION] Broken Text::CSV tests and possibly other ecosystem fallout

2017-09-05 Thread Parrot Raiser
Perl 5 programmers are used to being casual about closing file handles. Obviously, 6 requires a change of habits. A cultural shift, if that's not too pretentious a term. Perhaps it needs to be mentioned in large, friendly letters somewhere in the documentation? On 9/5/17, jn...@jnthn.net via RT w

Re: [perl #132030] [REGRESSION] Broken Text::CSV tests and possibly other ecosystem fallout

2017-09-05 Thread Parrot Raiser via RT
Perl 5 programmers are used to being casual about closing file handles. Obviously, 6 requires a change of habits. A cultural shift, if that's not too pretentious a term. Perhaps it needs to be mentioned in large, friendly letters somewhere in the documentation? On 9/5/17, jn...@jnthn.net via RT w

[perl #132033] [BUG] Set.WHICH clashes due to hashing

2017-09-05 Thread via RT
# New Ticket Created by Zefram # Please include the string: [perl #132033] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=132033 > Since commit 167a0edf, Set.WHICH now hashes the concatenated .WHICHes of the set's elements, pr

Re: [perl #130970] [BUG] Set.new confused by Nil

2017-09-05 Thread Zefram via RT
Brian S. Julin via RT wrote: >It is that Nil is also semantically special as a RHS of an assignment >or as a parameter. ... >This is mentioned in S02. Some of the specialness mentioned in S02 doesn't happen, such as .ACCEPTS returning Nil, and getting the default value of an optional parameter. Th

[perl #132029] Floppage of atomic tests

2017-09-05 Thread jn...@jnthn.net via RT
On Tue, 05 Sep 2017 00:36:34 -0700, n...@detonation.org wrote: > A golfed version that reliably fails: > > { > my Int $test-cont = 42; > ⚛$test-cont; > } > { > my atomicint $set = 0; > start { sleep 1; $set ⚛= 1 }; > until ⚛$set { } > } > > The important bit is the Int being r

[perl #132029] Floppage of atomic tests

2017-09-05 Thread jn...@jnthn.net via RT
On Tue, 05 Sep 2017 00:36:34 -0700, n...@detonation.org wrote: > A golfed version that reliably fails: > > { > my Int $test-cont = 42; > ⚛$test-cont; > } > { > my atomicint $set = 0; > start { sleep 1; $set ⚛= 1 }; > until ⚛$set { } > } > > The important bit is the Int being r

Re: [perl #130970] [BUG] Set.new confused by Nil

2017-09-05 Thread Zefram
Brian S. Julin via RT wrote: >It is that Nil is also semantically special as a RHS of an assignment >or as a parameter. ... >This is mentioned in S02. Some of the specialness mentioned in S02 doesn't happen, such as .ACCEPTS returning Nil, and getting the default value of an optional parameter. Th

Re: [perl #128943] [BUG] Set.WHICH confused by spaces

2017-09-05 Thread Zefram via RT
With commit 167a0edf the behaviour of Set.WHICH has changed in a manner relevant to this ticket. The .WHICHes of the elements are no longer concatenated with space separators, so spaces no longer confuse Set.WHICH as they used to. The element .WHICHes are now concatenated with '\0' separators, s

Re: [perl #128943] [BUG] Set.WHICH confused by spaces

2017-09-05 Thread Zefram
With commit 167a0edf the behaviour of Set.WHICH has changed in a manner relevant to this ticket. The .WHICHes of the elements are no longer concatenated with space separators, so spaces no longer confuse Set.WHICH as they used to. The element .WHICHes are now concatenated with '\0' separators, s

[perl #132032] [BUG] List.new loses Nil

2017-09-05 Thread via RT
# New Ticket Created by Zefram # Please include the string: [perl #132032] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=132032 > > (3, Nil) (3 Nil) > List.new(3, Nil) (3 (Any)) It is possible (as it should be) to put Nil in

[perl #132030] [REGRESSION] Broken Text::CSV tests and possibly other ecosystem fallout

2017-09-05 Thread jn...@jnthn.net via RT
On Tue, 05 Sep 2017 00:54:27 -0700, alex.jakime...@gmail.com wrote: > <[Tux]> CSV tests started to fail > <[Tux]> # at t/90_csv.t line 260 > <[Tux]> # expected: $[["1", "2", "3"], ["2", "a b", ""]] > <[Tux]> # got: $[["1", "2", "3"],] > <[Tux]> # Failed test 'AOH parse out' > > > Bisectable

[perl #132030] [REGRESSION] Broken Text::CSV tests and possibly other ecosystem fallout

2017-09-05 Thread jn...@jnthn.net via RT
On Tue, 05 Sep 2017 00:54:27 -0700, alex.jakime...@gmail.com wrote: > <[Tux]> CSV tests started to fail > <[Tux]> # at t/90_csv.t line 260 > <[Tux]> # expected: $[["1", "2", "3"], ["2", "a b", ""]] > <[Tux]> # got: $[["1", "2", "3"],] > <[Tux]> # Failed test 'AOH parse out' > > > Bisectable

[perl #132030] [REGRESSION] Broken Text::CSV tests and possibly other ecosystem fallout

2017-09-05 Thread Aleks-Daniel Jakimenko-Aleksejev via RT
The issue is likely in Text::CSV so it's not fully a rakudo bug. However, we probably have a bunch of broken modules in the ecosystem because of this. I guess we need a Toaster report and a bunch of PRs for missing .close calls to fix everything… On 2017-09-05 00:54:27, alex.jakime...@gmail.com wr

[perl #132030] [REGRESSION] Broken Text::CSV tests and possibly other ecosystem fallout

2017-09-05 Thread via RT
# New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev # Please include the string: [perl #132030] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=132030 > <[Tux]> CSV tests started to fail <[Tux]> # at t/90_csv.t line 260 <[

[perl #132029] Floppage of atomic tests

2017-09-05 Thread Aleks-Daniel Jakimenko-Aleksejev via RT
Oh. A crude way to reproduce it is: while :; do clear; PERL6LIB=lib ./perl6-m t/spec/S17-lowlevel/atomic-ops.t || break; done And just leave it running, it'll fail at some point. Get your system busy with something and it'll fail faster. On 2017-09-05 00:14:11, alex.jakime...@gmail.com wrote: >

[perl #132029] Floppage of atomic tests

2017-09-05 Thread via RT
# New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev # Please include the string: [perl #132029] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=132029 > Here's the output when it fails: ok 1 - Can do an atomic fetch from