On Wed, 1 Mar 2023 at 13:46, Dave Mitchell <davem@iabyn.com> wrote: > On Tue, Feb 28, 2023 at 01:27:06PM +0100, Leon Timmermans wrote: > > Yeah, at this point it's probably better to introduce this early in the > > next cycle. And possibly then enable it by default (even if we might not > > yet do that for production releases) to shake all possible issues out. > > We might want to leave temporarily enabling it until all the issues we > already know with CPAN have been fixed. For example, any XS module which > uses a custom OP or PP function is likely to break. > For what it's worth the branch has already help shake out a bug in Text::CSV_XS. If that precedent is not an anomaly it looks like XS modules that do not create PP functions that are broken by the branch have a defect already and the branch is a good way to find bugs. (Seems like a win to me) Sereal::Encoder/Decoder do support custom opcode stuff but afaik they did not break. Not sure why yet. Is it expected that some such code would still be fine? Yves -- perl -Mre=debug -e "/just|another|perl|hacker/"Thread Previous | Thread Next