The speed (improvement) of Rakudo

Hi, Is there some measurements regarding the speed of Rakudo? e.g. It would be nice to have a graph of some hand-picked operations measured at different points in time of the development of Rakudo and then graphed in a nice way. Is there anything like that? Gabor

Re: next

On Sat, Jun 17, 2017 at 4:19 AM, ToddAndMargo wrote: > On 06/16/2017 06:08 PM, Brandon Allbery wrote: >> >> On Fri, Jun 16, 2017 at 9:02 PM, ToddAndMargo > > wrote: >> >> I am afraid I am not understanding "next"

Re: next

On 06/16/2017 06:08 PM, Brandon Allbery wrote: On Fri, Jun 16, 2017 at 9:02 PM, ToddAndMargo > wrote: I am afraid I am not understanding "next" again. When you invoke it, does it pop you back at the start of the loop or just

Re: next

On Fri, Jun 16, 2017 at 9:02 PM, ToddAndMargo wrote: > I am afraid I am not understanding "next" again. > > When you invoke it, does it pop you back at the start of > the loop or just cough up the next value? > The former. Or you can think of it as jumping past everything

next

Hi All, I am afraid I am not understanding "next" again. When you invoke it, does it pop you back at the start of the loop or just cough up the next value? Many thanks, -T -- ~~~ Serious error. All shortcuts have disappeared. Screen. Mind. Both are blank.

Re: Perl 6 ignores SIGPIPE

I think it'd be cool to notice, and properly report, write errors, rather than silently ignoring them. Back when lwall was asking for things we wanted perl6 to do, I asked to be able to wrap builtins specifically so I could use Fatal qw(print). Yes, perl5 often ignores write errors, but no, I

Re: Perl 6 ignores SIGPIPE

> On 16 Jun 2017, at 14:10, Jan Ingvoldstad wrote: > > On Fri, Jun 16, 2017 at 12:13 PM, Elizabeth Mattijsen wrote: > > Failed to write bytes to filehandle: Broken pipe > in block at -e line 1 > > So it would appear this got fixed by the synchronous IO

Re: Perl 6 ignores SIGPIPE

On Fri, Jun 16, 2017 at 12:13 PM, Elizabeth Mattijsen wrote: > > > Failed to write bytes to filehandle: Broken pipe > in block at -e line 1 > > So it would appear this got fixed by the synchronous IO refactor, and will > be available in the 2017.06 release, which is scheduled

Re: getting help in the REPL

> On 14 Jun 2017, at 16:07, Gabor Szabo wrote: > On Wed, Jun 14, 2017 at 4:44 PM, Timo Paulssen wrote: >> WHY and WHEREFOR are "fully" supported, it's just that we've not put any >> pod into the core setting and we don't have helper code that loads it >>

Re: Perl 6 ignores SIGPIPE

> On 16 Jun 2017, at 08:34, Sean McAfee wrote: > > I see at > > http://www.moarvm.com/releases.html > > ...that as of the 2017.03 release, Perl 6 "ignores SIGPIPE by default." I > discovered this for myself when I piped a program that generates unlimited > output to the

Re: How do you call the variable types?

> On 16 Jun 2017, at 06:23, Gabor Szabo wrote: > > On Sat, Jun 10, 2017 at 9:38 AM, Brent Laabs wrote: >> I thought: >> $ is Scalar >> @ is Array >> % is Hash >> & is a function >> > > Reading this https://docs.perl6.org/language/containers I just found

Perl 6 ignores SIGPIPE

I see at http://www.moarvm.com/releases.html ...that as of the 2017.03 release, Perl 6 "ignores SIGPIPE by default." I discovered this for myself when I piped a program that generates unlimited output to the head utility, and the program did not exit when head was finished. Simple example: $