Front page | perl.perl5.porters |
Postings from March 2022
There are a few ideas for more "builtin::" functions still floating
around unfinished:
* `load` (RFC 0006) - still pending a PR
* created_as_{string,number} (Draft RFC 0017)
PR: https://github.com/Perl/perl5/pull/19524
I wonder if either or both could still go in to 5.35.11, in time to
make a 5.36.0 release. The only relevant guidance I can find in
documentation is in Porting/release_schedule.pod, which says:
2022-03-20 5.35.10 Sawyer X User-visible changes to
correctly functioning programs
freeze
2022-04-20 5.35.11 ? Full code freeze
It seems to me that simply adding a new builtin function is not a
*change* to a correctly functioning program. So the letter of the rules
still permits this before 5.35.11.
On the "for" side, adding the `created_as_*` functions would be a good
feature to go alongside the PV/IV flag stability and the new core
booleans and is_bool function. The combination overall makes a lot of
sense - adding much useful ability to places like JSON encoders et.al.,
as we have all written about a lot lately.
On the "against" side, it's still new code being added at this fairly
late stage.
But counter to that I'd say the actually-added code is tiny, just a
flags test function in the "builtin::" namespace. All the tricky PV/IV
flags changes have been in for a while now. This just exposes the
stored information more usefully to perl space.
I am as yet undecided. As the author of the PR, I'm keen to get it
merged. But with the PSC hat on, we have to think about pacing of
development work in the leadup to the next major release.
I'm open to thoughts either way - Opinions anyone?
--
Paul "LeoNerd" Evans
leonerd@leonerd.org.uk | https://metacpan.org/author/PEVANS
http://www.leonerd.org.uk/ | https://www.tindie.com/stores/leonerd/
Thread Next