David Mitchell

On Fri, May 03, 2024 at 09:43:25AM -0700, Paul Evans wrote: > If the value being assigned into an lvalue `vec()` is tainted, it > sometimes does and sometimes doesn't...

On Wed, May 08, 2024 at 04:24:44PM -0700, Hugo van der Sanden wrote: > In the first commit message, I don't understand the line `Overall, $pat > has the same...

I've just pushed a forced update. On Mon, May 13, 2024 at 03:11:46PM -0700, Hugo van der Sanden wrote: > I somehow missed that "A1B2C3" was the literal pattern: I've...

On Sat, Oct 22, 2022 at 03:02:18AM -0700, Yves Orton wrote: > Well, as I said /personally/ I would consider this a bug, but if we are not > going...

On Sat, Jan 07, 2023 at 10:01:15AM -0800, Yves Orton wrote: > The offset data has been doubled to hold a "start/end" and > "start_new/end_new" pairs. OPEN/CLOSE etc update start_new/end_new....

I *think* S_new_SV() should be made always defined, not just existing on DEBUG_LEAKING_SCALARS builds; but with the extra sv->sv_debug* and logging lines wrapped in ifdef DEBUG_LEAKING_SCALARS. Then the macro new_SV()...

On Tue, May 21, 2024 at 08:43:38PM -0700, mauke wrote: > ```perl > use v5.38; > > say __LINE__; > ``` > Code: > ``` > $ ./perl try.pl >...

On Wed, May 22, 2024 at 03:25:51AM -0700, mauke wrote: > Why do you think a deparse that outputs 9 (or 2) is correct when the > compiled code outputs...

On Wed, May 22, 2024 at 04:07:47AM -0700, mauke wrote: > Not necessarily, but the funny thing is that this case is mostly > unaffected by the change in blead....

LGTM. I'd suggest also mentioning briefly that the cloning process uses use a cache, so that if a particular SV address has already been duped, that duped SV is returned...