Closed robrwo closed 3 years ago
This is part of the RFC checklist. It mostly focuses on Moo/se. There are (last I counted), about 80+ CPAN modules to handle some aspects of OO, and I've encountered hand-rolled ones at clients. I can't cover all of them, so I mostly focused on Moo/se since they've traditionally been the winners. I've covered some of these topics in videos here and here.
Thus, I'll close this out because it will be covered in the checklist.
I keep reading the documentation and thinking "this is called 'x' in Moose why is it called 'y' in Cor?"
So I think a small paragraph (one or two sentences) explaining why something has a different name or a different function/method name will be helpful, not just in the RFCs but for people coming from those object systems.