Conversation
... which was triggered by introduction of 'use v5.42;'
|
I don't like this solution. It doesn't look correct, if it's not reasonable to warn about redefinition here then the reason for that should be explained. AFAICT, the problem is that |
Okay, but
Who wants to take on that refactoring? |
It is at line 147 of lib/overload.t that the warning is emitted. |
|
The test here is deliberately redefining the So:
To me the ideal behaviour would be:
|
|
#24777 maybe I learned even more about overloading internals, I'm not sure that was a good idea. |
... which was triggered by introduction of 'use v5.42;'
Fixes: GH #24774