|There's more than one way to do things|
Re^3: Cor—An object system for the Perl coreby 1nickt (Abbot)
|on Jun 01, 2020 at 21:11 UTC||Need Help??|
Neither does either proposed solution solve the problem.
I have a class. The class uses a bundle module. The bundle imports List::Util::any into the calling package.
I like to test my classes. I like to use Test::Most. If I use Test::Most with default imports I get an exception (under strictures).
Instructing Test::Most to not import Test::Deep in order to avoid this collision means that I cannot use the other methods in Test::Deep that I require.
Test::Most does not allow granular control over the exports of the modules it imports.
That's a design assumption: the user will either want all of Test::Deep or none of it. It limits the value of Test::Most.
I don't want to see similar design assumptions baked into Perl. No one set of assumptions can possibly meet everyones's needs.
It would be a mistake to put Cor or any other OOP framework into the Perl language.
The way forward always starts with a minimal test.