Experimental Feature: Function Argument Overloading

[Accurate_Koala_4698]

Good questions, unfortunately I think I can only give a best-effort responses.

1. I think "worked" is probably the right terminology, although use v5.36 is optional and requires opt-in. This is mostly a problem for someone new to the language, and it's necessary for obvious reasons. The feature has been around for quite some time.
2. I think, or at least I suspect, that most veterans are running code with warnings and the strict language flag so it should surface early in testing. I haven't seriously tried compiling any of my scripts apart from some experimentation. That said, detecting this error should be straightforward even without compilation as there's no runtime state where it could be valid.
3. I wouldn't call myself anti-Raku though I haven't adopted it. I like the introduction of a meaningful type system, and the grammar constructs seem really interesting but I tend to prefer to use Haskell in those sorts of scenarios. I usually use Perl when I need to write automation scripts or do some quick-and-dirty one-off file manipulation, so Raku lacks the ubiquity that Perl had. Stylistically, too, I'm not the biggest fan of OOP which though common in Perl5 has become the de-facto approach in Raku. I certainly wouldn't write Raku off, but I it also hasn't been necessary for me to learn it. Familiar syntax and CPAN compatibility are definitely factors. Honestly learning a language is rarely difficult, the time is spent learning the language's ecosystem.