Front page | perl.perl5.porters |
Postings from February 2023
On 2023-02-27 2:50 a.m., demerphq wrote: > On Sun, 26 Feb 2023 at 17:06, Dave Mitchell wrote: > The branch containing the first stage of my "make the stack ref-counted" > work is nearly ready for merging. In a default build, the core is mostly > unchanged: only when built with -DPERL_RC_STACK does it behave > differently. It needs testing on Windows. I need to decide whether to > merge soon or wait until after 5.38. > > I think it has to wait till 5.38, at least as far as normal policy goes. I guess > it depends on whether we consider this a contentious code-change, but given its > scale it seems like we should hold off. (It brings me no joy to say this BTW, id > be more than happy if my understanding was incorrect.) To be completely clear, in a default build, should all known XS also compile and run properly without alterations? Or does the "mostly unchanged" exclude some things that XS may be sensitive to? While this may be unfair to say, one possible reason to hold this back from 5.38 is if including it in 5.38 may make people uncomfortable in that version's maturity and safety such that adoption of the first Corinna features suffer. We finally after a long wait got some of Corinna in and its use should be encouraged, so we would want to minimize any reasons people would hold back on upgrading to 5.38 and taking advantage of Corinna. Whether for Corinna or otherwise, if there is any significant risk or non-confidence that a default build of Perl following the "make the stack ref-counted" merge is defective or incompatible, I would suggest that holding it for 5.40 in order for it to have more testing and proving time, may be best. However, those are my thoughts for the community as a whole. Just for myself as an individual, I'm ok to take the risk and use a 5.38 with the branch merged in. -- Darren DuncanThread Previous | Thread Next