[perl #130611] hash slice assignment doesn't work for custom class

On Sat, 21 Jan 2017 10:07:46 -0800, sml...@gmail.com wrote: > The documentation > > makes it clear that ASSIGN-KEY is merely an optional performance > optimization that the compiler may or may not use instead of AT-KEY in > some ca

Re: [perl #130638] [LTA] X::Seq don't say which Seq the exception occurred on

I think this is a basic misunderstanding about what an Iterator is and what a Seq. The basic thing is the Iterator. .Seq is nothing but method Seq() { Seq.new(self.iterator) } In other words, a Seq is just a wrapper around an Iterator. In general, you shouldn’t be asking a Seq for its Iterator

[perl #130494] [CONC] [PERF] Using Proc::Async with tap leads to memory leak

On Tue, 10 Jan 2017 14:30:27 -0800, ronaldxs wrote: > Both code sample and htmlify.p6 still leak for me. Sorry. > Yes, I wasn't entirely clear - there was more than one issue, and so fixing the first couple of issues only improved things rather than fully resolved them. I just bumped MOAR_REVIS

Re: [perl #130638] [LTA] X::Seq don't say which Seq the exception occurred on

On 25.01.2017 10:47, Samantha McVey wrote: > On Wednesday, 25 January 2017 01.45.59 PST you wrote: >> On Tue, 24 Jan 2017 23:15:32 -0800, samant...@posteo.net wrote: >> > CODE: >> > my Seq $thing = (1,3,4).Seq; $thing.iterator; $thing.iterator >> > >> > STDERR: >> > This Seq has already been ite

Re: [perl #130638] [LTA] X::Seq don't say which Seq the exception occurred on

On Wednesday, 25 January 2017 01.45.59 PST you wrote: > On Tue, 24 Jan 2017 23:15:32 -0800, samant...@posteo.net wrote: > > CODE: > > my Seq $thing = (1,3,4).Seq; $thing.iterator; $thing.iterator > > > > STDERR: > > This Seq has already been iterated, and its values consumed > > (you might solve t