[perl #131654] [bug] 'does' is not threadsafe

2017-06-26 Thread jn...@jnthn.net via RT
On Sun, 25 Jun 2017 23:14:00 -0700, ben-goldb...@hotmail.com wrote: > Here's an IRC snippet showing the problem: > > m: await start { my $a = "strange"; $a does role Test { > }; } xx 16 > <+camelia> rakudo-moar 9936a3: OUTPUT: «Tried to get the result of a > broken Promise␤ in block at line 1␤

[perl #131654] [bug] 'does' is not threadsafe

2017-06-26 Thread jn...@jnthn.net via RT
On Sun, 25 Jun 2017 23:14:00 -0700, ben-goldb...@hotmail.com wrote: > Here's an IRC snippet showing the problem: > > m: await start { my $a = "strange"; $a does role Test { > }; } xx 16 > <+camelia> rakudo-moar 9936a3: OUTPUT: «Tried to get the result of a > broken Promise␤ in block at line 1␤

[perl #131656] Feature request, for fewer {}

2017-06-26 Thread Zoffix Znet via RT
On Mon, 26 Jun 2017 02:02:22 -0700, ben-goldb...@hotmail.com wrote: > This is a request for a new syntactic feature for perl6, a keyword > named 'unlisp' or 'unbrace'. > > This new keyword would act almost exactly like a '{', with the > difference that when a matching '}' is found (or the end of f

[perl #131656] Feature request, for fewer {}

2017-06-26 Thread Zoffix Znet via RT
On Mon, 26 Jun 2017 02:02:22 -0700, ben-goldb...@hotmail.com wrote: > This is a request for a new syntactic feature for perl6, a keyword > named 'unlisp' or 'unbrace'. > > This new keyword would act almost exactly like a '{', with the > difference that when a matching '}' is found (or the end of f

[perl #131656] Feature request, for fewer {}

2017-06-26 Thread via RT
# New Ticket Created by Benjamin Goldberg # Please include the string: [perl #131656] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=131656 > This is a request for a new syntactic feature for perl6, a keyword named 'unlisp' o

[perl #131608] [BUG] Apparent improper handling of SIGPIPE

2017-06-26 Thread Leon Timmermans via RT
On Tue, 20 Jun 2017 06:12:54 -0700, jani wrote: > According to a brief mail discussion on perl6-users > (https://www.nntp.perl.org/group/perl.perl6.users/2017/06/msg3905.html > and subsequent messages), Rakudo seems to improperly handle piping > with e.g. head, and therefore most likely any other k