In some packages on #metacpan you can see what the minimum Perl version must be. Is this binding? Looks to me like most packages often support very low Perl versions. Understandable, if you want the package to work with very old
Perl versions, but surely this prevents new #perl features from spreading very slowly?
Recently worked a bit with Getopt:: Long. Quite cool that it is possible to pass a subroutine for a command line argument and thus perform sanity checks right away 
https://github.com/RotherOSS/otobo/commit/7618b8ea8aef9178739662169ccf3487472acc30
@KO6YQ #Perl version “5.38.1a” appears to have been a botched test release that escaped to #CPAN per this post from @leonerd: https://www.nntp.perl.org/group/perl.perl5.porters/2023/11/msg267357.html
Please stand by for the correct version 5.38.x release.
Note that “perl-5.38.1a” on that #MetaCPAN page is grayed out, which indicates it is not actually the latest release.
@ChristosArgyrop @Perl I don’t think it searched #CPAN or #MetaCPAN, because “BinaryTree” doesn’t exist there. It’s merely suggesting a package name.
If it actually searched CPAN it would tell you about something like https://metacpan.org/pod/Tree::Binary
And if it were truly CPAN-aware it would tell you to name your package Local::BinaryTree so you don’t get surprised later when another #Perl package from outside preempts your name: https://pause.perl.org/pause/query?ACTION=pause_namingmodules#Local
