Hi Ikegami, thanks for your reply. I was expressing alarm not at the introduction of smartmatch back in the day, but at the way in which it has been reimplemented in 5.27, i.e., apparently *not* following the policy its original introduction gave rise to. This is according to the articles mentioned above and my reading of the p5p thread, specifically that new keywords that have since almost universally met with scorn, were merged into blead with little or no discussion on the list, let alone off it.
I know that you are a p5p regular, perhaps you know different. Your perspective would be welcomed.
You can say that any sensible production code has always avoided smartmatch and given/when, but in fact it has been used in several CPAN modules that are themselves widely used in production, e.g. Type::Tiny and Try::Tiny, so isn't even a developer who has him/herself studiously avoided it because it's experimental, at risk of their code breaking through such changes?
In reply to Re^4: Update to smartmatch
by 1nickt
in thread Update to smartmatch
by stevieb
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |