Re: Observations from a C++/Python developer that never used Perl5

> > it is combining too many new things at once: Well, it is meant to be the up-front example of everything at once before the step-by-step... > * BUILD > * new These are the heart of construction. I don't think there's any avoiding that in a class tutorial. * submethod > * bless These

Re: Observations from a C++/Python developer that never used Perl5

On Thu, Sep 8, 2016 at 12:25 AM, Kaare Rasmussen wrote: > I wonder what you miss from https://docs.perl6.org/language/classtut. To > me, it explains the hows and whys very thoroughly. Now, I now people have > been hard at work improving the documentation, so if you can point to

[perl #129228] [SEGV] concurrent network access segfaults in libmoar.so

# New Ticket Created by Robert Lemmen # Please include the string: [perl #129228] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=129228 > this simple program: ---8<--- use v6;

Re: Justification for the "reversed" instruction format

On Thu, Sep 8, 2016 at 9:23 AM Aaron Sherman a...@ajs.com wrote: I don't know Haskell, but isn't flip just: > > sub flip() { -> $b, $a, |c { f($a, $b, |c) } } > > And then: > > perl6 -e 'sub flip() { -> $a, $b, |c { f($b, $a, |c) } }; my = flip > yas(1,2,3)' > 213 >

Re: Justification for the "reversed" instruction format

Ah, nice, good to know my concern was unwarranted. On Thu, Sep 8, 2016 at 3:04 PM Aaron Sherman wrote: > In Perl 6, we apply those constraints when you pass off the call to the > ultimate recipient, and that's important because that recipient can have > multiple signatures (and

[perl #128123] [JVM] failing test in S03-metaops/hyper.t after change from postfix:<++> to prefix:<++>

And now a lot of tests from roast exploded with "Expected a native int argument for '$a'" after this commit introduced two uses of postfix:<++> and postfix:<--> in lib/Test.pm6: https://github.com/rakudo/rakudo/commit/ffb5789f7eef1157c7556897c4805569df4f7aa4 Modifying the two relevant lines

[perl #129234] [CONC] `.hyper` and `.race` resume after exceptions

# New Ticket Created by Sam S. # Please include the string: [perl #129234] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=129234 > If you `die` inside a `map/for` that is being `hyper/race`d... for (1..1).hyper { die };

Re: Justification for the "reversed" instruction format

In Perl 6, we apply those constraints when you pass off the call to the ultimate recipient, and that's important because that recipient can have multiple signatures (and signatures can be added *after* you define the flip). For example: $ cat foo.p6 sub flip() { -> $b, $a, |c { f($a, $b, |c) }

[perl #129228] [SEGV] concurrent network access segfaults in libmoar.so

I'm unable to reproduce this on HEAD Rakudo even with $n set to 40 and RAKUDO_MAX_THREADS set to 50. What is your perl6 version (perl6 -v). Are you able to try this against HEAD [^1]? Yesterday a fix went in addressing issues in sockets and threads; and recently there have been many other

[perl #128862] [CONC] IO::Socket::Async server throws uncatchable exception in case of encoding errors

On Sat Aug 06 11:25:38 2016, sml...@gmail.com wrote: > Golfed program to demonstrate the problem: > > my $server = IO::Socket::Async.listen('localhost', ); > $server.tap: -> $conn { > $conn.Supply.tap: -> $message { say $message.perl } > } > > my $client =

The use of $!attr vs self.attr in core libraries

In working with Range a while back, I was frustrated to find that writing a subclass that wanted to override an accessor (e.g. for $.min and $.max) was quite difficult because most methods ignored the accessors and called $!min and $!max or wrote to them directly. If I really wanted to change the

Re: Justification for the "reversed" instruction format

I don't know Haskell, but isn't flip just: sub flip() { -> $b, $a, |c { f($a, $b, |c) } } And then: perl6 -e 'sub flip() { -> $a, $b, |c { f($b, $a, |c) } }; my = flip yas(1,2,3)' 213 Aaron Sherman, M.: P: 617-440-4332 Google Talk, Email and Google Plus: a...@ajs.com Toolsmith, developer,

Re: Observations from a C++/Python developer that never used Perl5

> As I recall it, macros where left out of the initial implementation. So you > have to wait for another Christmas Present :-) The version of macros that was available in Rakudo when the 6.c spec was cut was released with the compiler; It's marked experimental and is therefore subject to change,

Re: Observations from a C++/Python developer that never used Perl5

On Thu, Sep 8, 2016 at 6:41 AM, Kamil Kułaga wrote: > In perl6 default way is to not write new, BUILD or BUILDALL and also > not to write accessors. When you create object you can provide > attributes to initialize, default accessors are generated if field is > declared with

[perl #128545] [LTA] [UNI] Date.new(Str) poor error message for digit with diacritic

Thanks for the report. Fixed in https://github.com/rakudo/rakudo/commit/a2b6f74be1 Tests added in https://github.com/perl6/roast/commit/3ed2af4c42

[perl #129221] [BUG][UNI] Combinators get matched by regex even when no ignoremark is set

Not a bug. See also http://irclog.perlgeek.de/perl6-dev/2016-09-08#i_13170729

[perl #129227] [SEGV] Concatenation of a large number of combining characters

# New Ticket Created by Zoffix Znet # Please include the string: [perl #129227] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=129227 > m: 7 ~ "\x[308]" x 100_000 rakudo-moar 7925d6: OUTPUT«WARNINGS for :␤Useless use of

Re: Observations from a C++/Python developer that never used Perl5

On Thu, Sep 8, 2016 at 4:00 AM, Joseph Garvin wrote: > * I can find no concise easy-to-understand explanation for how to define > what other languages would call constructors. Instead there is a mess of > bless, magic inside Mu, new, BUILD, BUILDALL... It's not clear