On Fri, 2013-06-14 at 19:26 +1000, Kieren Diment wrote:
> Presumably CPAN testing of a blead perl with smartmatch removed/deprecated could pick that up pretty quickly.
Automated CPAN testing occurs on new releases of modules only doesn't it
or is there comprehensive testing of every current release on CPAN when
a new perl is being prepared for release?
Even if you catch everything in CPAN that doesn't address the risk for
in house libraries which is an issue for many of those using perl in
production and doesn't address application code using smart match or
given/when.
My point was more about the difficulty this uncertainty causes in
assessing the risk that it will be necessary to rewrite libraries and
applications.