Re: [perl #132066] [BUG] Code blocks cause backtracking fail in `|` alternation with ratcheting

2017-09-12 Thread Dan Zwell via RT
Right; :ratchet turns off backtracking, but the `|` operator still needs to find the best match. I should have said "LTM" rather than backtracking, since that's what I was referring to--trying multiple terms to find the best match. On Tue, Sep 12, 2017 at 2:20 PM Patrick R. Michaud via RT <

[perl #122504] [TESTNEEDED] 'return' invoked outside of a routine should throw an exception

2017-09-12 Thread Brian S. Julin via RT
On Sun, 10 Sep 2017 11:22:29 -0700, sml...@gmail.com wrote: > A `return` outside a routine now always seems to throw a run-time > error, as it should: > > $ perl6 -e 'return' > Attempt to return outside of any Routine > in block at -e line 1 > > $ perl6 -e '{ return }' > Attempt to return

[perl #126332] [TESTNEEDED] .assuming ignores anything from the second argument onwards in Rakudo

2017-09-12 Thread Brian S. Julin via RT
On Tue, 12 Sep 2017 08:55:37 -0700, sml...@gmail.com wrote: > On Mon, 12 Oct 2015 05:33:13 -0700, masak wrote: > > m: my := ('hello world'); say f(0, 2); > > rakudo-moar 70a94d: OUTPUT«hello world␤» > > m: say ('hello world')(0, 2) > > rakudo-moar 70a94d: OUTPUT«hello world␤» > > [...] > >

[perl #132073] [BUG] isa method errors when called on a subset type object

2017-09-12 Thread via RT
# New Ticket Created by David Warring # Please include the string: [perl #132073] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=132073 > current behavior of isa method on a subset: % perl6 -v This is Rakudo version

[perl #127947] [CONC] Hangs in spectests with test that calls .quit on Supplier

2017-09-12 Thread Christian Bartolomaeus via RT
On Fri, 22 Apr 2016 12:20:54 -0700, barto...@gmx.de wrote: > On Thu Apr 21 04:41:32 2016, barto...@gmx.de wrote: > > [...] > > A somewhat golfed example of the hanging code is: > > > > $ perl6-j -e 'my $r = Supplier.new; my $s = $r.Supply; my $c = > > $s.Channel; my $p = start { for @$c { } }; for

[perl #125293] [BUG] Match objects don't roundtrip through .perl

2017-09-12 Thread Christian Bartolomaeus via RT
The tests in question have been unfudged with roast commit https://github.com/perl6/roast/commit/6db316eaae. (This was probably fixed with merging the 'uncurse' branch.) The last example from the last comment (using EVAL) works as expected, too: $ ./perl6-m -e 'say Map.new("a", 42).perl.EVAL'

[perl #126139] [BUG] [GLR] nested lazy cross operators confuse the continuations

2017-09-12 Thread Sam S. via RT
Merged two commits that I'm pretty sure are about the same issue. On Tue, 22 Sep 2015 18:09:54 -0700, larry wrote: > 18:00 < TimToady> m: my @v := [1, 2]; my \step1 = 8 X* ^4; my \step2 = @v > X+> step1; say step2 X% 256; > 18:00 <+camelia> rakudo-moar 631ac4: OUTPUT«===SORRY!===␤Cannot invoke

Re: [perl #129941] [PERF] [IO] Perl 6 text file line read is much slower than Perl 5

2017-09-12 Thread Tom Browder via RT
On Tue, Sep 12, 2017 at 09:23 jn...@jnthn.net via RT < perl6-bugs-follo...@perl.org> wrote: > On Mon, 24 Oct 2016 03:27:55 -0700, tbrowder wrote: > > On Sat Oct 22 04:24:15 2016, tbrowder wrote: > > > See for a suite > > > of tests that show

Re: [perl #129941] [PERF] [IO] Perl 6 text file line read is much slower than Perl 5

2017-09-12 Thread Tom Browder
On Tue, Sep 12, 2017 at 09:23 jn...@jnthn.net via RT < perl6-bugs-follo...@perl.org> wrote: > On Mon, 24 Oct 2016 03:27:55 -0700, tbrowder wrote: > > On Sat Oct 22 04:24:15 2016, tbrowder wrote: > > > See for a suite > > > of tests that show

[perl #132016] [TESTNEEDED] Supply.merge and signals ( signal(SIGTERM).merge(signal(SIGINT)) )

2017-09-12 Thread Aleks-Daniel Jakimenko-Aleksejev via RT
Sorry, it was marked as “resolved”, but I don't see any mention of tests. On 2014-09-16 07:51:34, elizabeth wrote: > 16:48:20] jnthn: sanity check: we should allow more than > one signal to be tapped at a time, right ? > [16:49:10] lizmat: aye > [16:49:32] putting this in a file: > [16:49:34]

[perl #130612] [REGEX] [@LARRY] LTM doesn't use text order for tie break as expected

2017-09-12 Thread Sam S. via RT
Confirmed on IRC that this is a bug. Relevant log¹ (edited for clarity): Is it intended that LTM prefers \d and <[0..9]> over and <:Number>, as a tie-breaker? (re. RT #130612) no, that wasn't intended m: say '1' ~~ / \d | {

[perl #126332] [BUG] .assuming ignores anything from the second argument onwards in Rakudo

2017-09-12 Thread Sam S. via RT
On Mon, 12 Oct 2015 05:33:13 -0700, masak wrote: > m: my := ('hello world'); say f(0, 2); > rakudo-moar 70a94d: OUTPUT«hello world␤» > m: say ('hello world')(0, 2) > rakudo-moar 70a94d: OUTPUT«hello world␤» > [...] It works fine now: ➜ say ("hello world")(0, 2); he ➜ say { @_

[perl #122790] [CONC] Tapping multiple signals fails strangely

2017-09-12 Thread jn...@jnthn.net via RT
On Tue, 16 Sep 2014 07:51:34 -0700, elizabeth wrote: > 16:48:20] jnthn: sanity check: we should allow more than > one signal to be tapped at a time, right ? > [16:49:10]lizmat: aye > [16:49:32] putting this in a file: > [16:49:34] signal(SIGHUP).act: -> { }; >

[perl #122790] [CONC] Tapping multiple signals fails strangely

2017-09-12 Thread jn...@jnthn.net via RT
On Tue, 16 Sep 2014 07:51:34 -0700, elizabeth wrote: > 16:48:20] jnthn: sanity check: we should allow more than > one signal to be tapped at a time, right ? > [16:49:10]lizmat: aye > [16:49:32] putting this in a file: > [16:49:34] signal(SIGHUP).act: -> { }; >

[perl #124005] [CONC] Cannot read from STDIN in a thread on windows console

2017-09-12 Thread jn...@jnthn.net via RT
On Fri, 19 Aug 2016 12:04:15 -0700, c...@zoffix.com wrote: > Tests appear to exist in t/spec/S16-io/handles-between-threads.t And have been fully passing since earlier this year when the issue of handles between threads was addressed; resolving.

[perl #124005] [CONC] Cannot read from STDIN in a thread on windows console

2017-09-12 Thread jn...@jnthn.net via RT
On Fri, 19 Aug 2016 12:04:15 -0700, c...@zoffix.com wrote: > Tests appear to exist in t/spec/S16-io/handles-between-threads.t And have been fully passing since earlier this year when the issue of handles between threads was addressed; resolving.

[perl #125230] [BUG] Reading from $*IN in a sub process' start {} hangs

2017-09-12 Thread jn...@jnthn.net via RT
On Thu, 21 May 2015 12:50:18 -0700, tony.od...@live.com wrote: > Encountered the following problem implementing Event::Emitter between > processes. This code will run forever as .read(1) forever reads > nothing from $*IN > > > #!/usr/bin/env perl6 > > > > > my $p = Proc::Async.new('perl6',

[perl #125230] [BUG] Reading from $*IN in a sub process' start {} hangs

2017-09-12 Thread jn...@jnthn.net via RT
On Thu, 21 May 2015 12:50:18 -0700, tony.od...@live.com wrote: > Encountered the following problem implementing Event::Emitter between > processes. This code will run forever as .read(1) forever reads > nothing from $*IN > > > #!/usr/bin/env perl6 > > > > > my $p = Proc::Async.new('perl6',

[perl #126692] [RFC] wrong line number in error message using Promise

2017-09-12 Thread jn...@jnthn.net via RT
On Fri, 20 Nov 2015 08:19:56 -0800, mt1...@gmail.com wrote: > Hi, > > When using 'my $p = Promise.start($code)' and die in that code for some > reason, I will get the die error message but the line number is of the > 'await $p' line. It would be more helpful to have the line number of the >

[perl #126692] [RFC] wrong line number in error message using Promise

2017-09-12 Thread jn...@jnthn.net via RT
On Fri, 20 Nov 2015 08:19:56 -0800, mt1...@gmail.com wrote: > Hi, > > When using 'my $p = Promise.start($code)' and die in that code for some > reason, I will get the die error message but the line number is of the > 'await $p' line. It would be more helpful to have the line number of the >

[perl #129941] [PERF] [IO] Perl 6 text file line read is much slower than Perl 5

2017-09-12 Thread jn...@jnthn.net via RT
On Mon, 24 Oct 2016 03:27:55 -0700, tbrowder wrote: > On Sat Oct 22 04:24:15 2016, tbrowder wrote: > > See for a suite > > of tests that show the differences. > > Suite has been updated considerably. In a benchmark on my local machine, after

[perl #129941] [PERF] [IO] Perl 6 text file line read is much slower than Perl 5

2017-09-12 Thread jn...@jnthn.net via RT
On Mon, 24 Oct 2016 03:27:55 -0700, tbrowder wrote: > On Sat Oct 22 04:24:15 2016, tbrowder wrote: > > See for a suite > > of tests that show the differences. > > Suite has been updated considerably. In a benchmark on my local machine, after

[perl #130417] [CONC] Take care of cas

2017-09-12 Thread jn...@jnthn.net via RT
On Tue, 27 Dec 2016 12:32:50 -0800, alex.jakime...@gmail.com wrote: > https://github.com/rakudo/rakudo/blob/9594a3ece38ca212023cf3ece7405d955303db13/src/core/asyncops.pm#L50 > > I thought I killed that off once > I did in 539b5f44ef3f pre-xmas > Because I thought it was pretty ridiculous

[perl #130417] [CONC] Take care of cas

2017-09-12 Thread jn...@jnthn.net via RT
On Tue, 27 Dec 2016 12:32:50 -0800, alex.jakime...@gmail.com wrote: > https://github.com/rakudo/rakudo/blob/9594a3ece38ca212023cf3ece7405d955303db13/src/core/asyncops.pm#L50 > > I thought I killed that off once > I did in 539b5f44ef3f pre-xmas > Because I thought it was pretty ridiculous

[perl #131387] `is default` value not applied to attributes by default

2017-09-12 Thread jn...@jnthn.net via RT
On Sat, 27 May 2017 19:35:53 -0700, c...@zoffix.com wrote: > $z is `Nil` without my having to assign anything, while `$!z` is Any. > To make `$!z` Nil I also have to assign Nil to it: > > m: my $z is default(Nil); dd $z;class Foo { has $!z is > default(Nil); method x { dd $!z } }.new.x >

[perl #131387] `is default` value not applied to attributes by default

2017-09-12 Thread jn...@jnthn.net via RT
On Sat, 27 May 2017 19:35:53 -0700, c...@zoffix.com wrote: > $z is `Nil` without my having to assign anything, while `$!z` is Any. > To make `$!z` Nil I also have to assign Nil to it: > > m: my $z is default(Nil); dd $z;class Foo { has $!z is > default(Nil); method x { dd $!z } }.new.x >

Re: [perl #132066] [BUG] Code blocks cause backtracking fail in `|` alternation with ratcheting

2017-09-12 Thread Patrick R. Michaud via RT
On Mon, Sep 11, 2017 at 09:48:01AM -0700, Dan Zwell wrote: > > `|` matches the longest input: > > 'ab' ~~ / ^:ratchet [ . | .. ] $ / > ｢ab｣ > > If the regex contains empty code blocks, backtracking fails: > > 'ab' ~~ / ^:ratchet [ {}. | {}.. ] $ / > Nil Isn't the whole point of :ratchet to turn

Re: [perl #132066] [BUG] Code blocks cause backtracking fail in `|` alternation with ratcheting

2017-09-12 Thread Patrick R. Michaud
On Mon, Sep 11, 2017 at 09:48:01AM -0700, Dan Zwell wrote: > > `|` matches the longest input: > > 'ab' ~~ / ^:ratchet [ . | .. ] $ / > ｢ab｣ > > If the regex contains empty code blocks, backtracking fails: > > 'ab' ~~ / ^:ratchet [ {}. | {}.. ] $ / > Nil Isn't the whole point of :ratchet to turn