Bug has been open a while, and I have not forgotten it, I had just not reached
a final decision. After further thought I'm closing this WONTFIX. It would
needlessly complicate our grapheme concatenation and in addition I believe it
may break some of the grapheme concatenation tests.
On behalf of the Rakudo development team, I’m very happy to announce the
July 2017 release of Rakudo Perl 6 #113. Rakudo is an implementation of
Perl 6 on the Moar Virtual Machine[^1].
This release implements the 6.c version of the Perl 6 specifications.
It includes bugfixes and optimizations on
Thank you!
This helped us solve a major headache we had with processes hanging
around after the tests have finished:
https://github.com/Bailador/Bailador/issues/194
regards
Gabor
I fudged the flopping test for this ticket in
https://github.com/perl6/roast/commit/4748a283e1
I fudged the flopping test for this ticket in
https://github.com/perl6/roast/commit/4748a283e1
# New Ticket Created by Zoffix Znet
# Please include the string: [perl #131755]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131755 >
The original failure was in t/spec/S32-io/open.t test that I golfed down to the
following
Tests in
https://github.com/perl6/roast/commit/b1f116fdd5181274cda1a520194488da82c10a7e
Tests in
https://github.com/perl6/roast/commit/b1f116fdd5181274cda1a520194488da82c10a7e
On Fri, 15 Jul 2016 02:45:51 -0700, mt1...@gmail.com wrote:
> Hi,
>
> Old code gives now error in Rakudo version 2016.06-234-g0189851 built on
> MoarVM version 2016.06-9-g8fc21d5.
>
> Code is
>
>sub encode-int32 ( Int:D $i --> Buf ) is export {
> my int $ni = $i;
> return Buf.new(
On Sat, 15 Jul 2017 07:15:05 -0700, jan-olof.hen...@bredband.net wrote:
> On Tue, 31 Jan 2017 09:05:52 -0800, c...@zoffix.com wrote:
> > I dug at this bug a few months back, but lost my notes on my
> > findings.
> >
> > As I recall it, the 128655 happens in BOOTSTRAP.nqp in
> > find_best_dispatchee
On Sat, 15 Jul 2017 09:44:28 -0700, jan-olof.hen...@bredband.net wrote:
> On Mon, 27 Feb 2017 06:55:46 -0800, mt1...@gmail.com wrote:
> > Hi,
> >
> > In Rakudo version 2017.02-56-g9f10434 built on MoarVM version
> > 2017.02-7-g3d85900
> > implementing Perl 6.c I observed the following;
> >
> > Ass
On Mon, 27 Feb 2017 06:55:46 -0800, mt1...@gmail.com wrote:
> Hi,
>
> In Rakudo version 2017.02-56-g9f10434 built on MoarVM version
> 2017.02-7-g3d85900
> implementing Perl 6.c I observed the following;
>
> Assume that a distribution is at /x/y (on Unix) then;
>
> 1) when no environment variab
On Sat, Jul 15, 2017 at 10:23 AM, Gabor Szabo wrote:
> If I understand correctly, then this means Ctrl-C sends a SIGINT to
> both the main process I ran and the child process I created using
> Proc::Async. When I run kill -2 PID it only sends the SIGINT to the
> process I mentioned with PID.
> (
Hi,
Brandon, thanks for the explanation.
If I understand correctly, then this means Ctrl-C sends a SIGINT to
both the main process I ran and the child process I created using
Proc::Async. When I run kill -2 PID it only sends the SIGINT to the
process I mentioned with PID.
(Which in my case was t
On Tue, 31 Jan 2017 09:05:52 -0800, c...@zoffix.com wrote:
> I dug at this bug a few months back, but lost my notes on my findings.
>
> As I recall it, the 128655 happens in BOOTSTRAP.nqp in
> find_best_dispatchee() the non-native candidate ends up being first in
> the list and that's why it's use
On Sat, Jul 15, 2017 at 8:34 AM, Brandon Allbery
wrote:
> Ctrl-C sends SIGINT to all processes in the terminal's foreground process
> group. There is no concept of "current process" on a terminal; Unixlike
> systems are multitasking, and all processes in the process group have
> access to the ter
On Sat, Jul 15, 2017 at 6:50 AM, Gabor Szabo wrote:
> If I run this in one terminal and run "ps axuw" in another terminal I
> see 2 processes running.
> If I press Ctrl-C in the terminal where I launched the program, both
> processes are closed.
>
> OTOH If I run "kill PID" with the process ID of
On Sun, 25 Dec 2016 09:50:17 -0800, c...@zoffix.com wrote:
> zoffix@VirtualBox:~$ perl6 -e 'my int $x = 4; say $x || 2'
> 1
> zoffix@VirtualBox:~$ perl6 --optimize=off -e 'my int $x = 4; say $x ||
> 2'
> 4
> zoffix@VirtualBox:~$ perl6 -v
> This is Rakudo version 2016.11-182-gea28845 built on MoarVM
On Fri, 14 Jul 2017 13:31:42 -0700, jan-olof.hen...@bredband.net wrote:
> On Fri, 07 Oct 2016 14:03:39 -0700, barto...@gmx.de wrote:
> > I think the p6bool is removed here:
> > https://github.com/rakudo/rakudo/blob/605f272881a76f0c5a9e352670a1e61eaa627ca6/src/Perl6/Optimizer.nqp#L1300
> >
> > As fa
This bug is still present in
This is Rakudo version 2017.06-251-g23ad2c388 built on MoarVM version
2017.06-91-g146c8fcc
implementing Perl 6.c.
Hi,
I don't understand this, and I wonder could shed some light on the situation?
I have the following experimental program:
use v6;
my $proc = Proc::Async.new($*EXECUTABLE, "-e", "sleep 2; say 'done'");
$proc.stdout.tap: -> $s { print $s };
my $promise = $proc.start;
await $promise;
If I r
A possibly better way to phrase it:
===SORRY!=== Error while compiling [...]
Constant "foo" is followed by another term at [...]
--> say foo⏏ 4;
If your meant to refer to the subroutine "foo" declared at [...],
then either:
* Use `foo(...)` to disambiguate.
* Rename
# New Ticket Created by Sam S.
# Please include the string: [perl #131754]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131754 >
A more helpful error message than just the generic "Two terms in a row"
could be thrown when t
23 matches
Mail list logo
