Re: [perl #132226] AutoReply: "impossible" undefined value in concurrent ENTER phasers

2017-11-10 Thread David Lowe via RT
This crash still occurs with rakudo 2017.10. On Thu, Oct 5, 2017 at 9:38 PM, perl6 via RT wrote: > Greetings, > > This message has been automatically generated in response to the > creation of a trouble ticket regarding: > ""impossible" undefined value in concurrent ENTER phasers", > a s

Re: [perl #132225] AutoReply: segmentation fault while concurrently updating SetHash

2017-11-10 Thread David Lowe via RT
This crash still occurs with rakudo 2017.10. On Thu, Oct 5, 2017 at 9:10 PM, perl6 via RT wrote: > Greetings, > > This message has been automatically generated in response to the > creation of a trouble ticket regarding: > "segmentation fault while concurrently updating SetHash", > a sum

Re: [perl #132042] [BUG] rakudo hangs while concurrently walking trees

2017-09-06 Thread J . David Lowe via RT
> On Sep 6, 2017, at 1:57 PM, Elizabeth Mattijsen via RT > wrote: > > >> On 6 Sep 2017, at 22:46, J . David Lowe (via RT) >> wrote: >> >> # New Ticket Created by J . David Lowe >> # Please include the string: [perl #132042] >> # in the

Re: [perl #131983] [BUG] mixin thread safety

2017-08-29 Thread J . David Lowe via RT
Agreed. In that case, the threads are just racing to observe a mutating value while it's in the "expected" state. I will add my voice to the chorus calling for either making roles into closures, or producing a compile-time warning or error. It's tempting to use roles to "monkey patch", and woul