Paul Evans

Furthermore, while the odd use of the `\&stringify` coderef from before either sub was created does not yield a warning, with the new warning code added by my #21915 it...

Closing as not-a-bug

> This will print `true`, which means the `use`/`no` pair didn't return to the previous state. Mmmm. Yes that's a fun one indeed. But compare it to features, strict or...

This entire PR and the wider "tombstone" mechanism are now being abandoned, in favour of the simpler model of "you can't get rid of lexicals". Which means `use VERSION` will...

> 1. For those who haven't been following along ... what is the "tombstone" behavior that is being eliminated? That term doesn't appear in our documentation. It's all really new,...

This can all be abandoned now. We've already removed all the tombstone related logic from builtin and `use VERSION`, and #22063 will remove the entire concept.

Is this a new issue in 5.39? I.e. is it a release blocker, or has it been around since at least 5.38 if not earlier? Additionally, I see some recent...

Since github doesn't follow a symlink in order to render `CONTRIBUTING.pod`, why don't we just copy it? In order to prevent it getting out of sync with the real one,...

Hmm. Specifically it's about `Concise`: ``` $ ./perl -Ilib -MO=Concise -e 'use v5.39' panic: invalid pad in intro_my: 0x565259cf7920[0x565259d179f8] at -e line 1. $ ./perl -Ilib -e 'use v5.39' (ok)...

Hrm; gdb doesn't show much more of any real excitement: ``` $ gdb --args ./perl -Ilib -MO=Concise -e 'use v5.39; no v5.39' ... (gdb) break Perl_croak Breakpoint 1 at 0x45c745:...