"An import list", you say? Who would ever need to pass an import list to an object oriented module?

...except that import lists are sometimes used for other purposes. An example would be use strict 'vars';, where 'vars' is passed to  ->import() so that the import routine can alter a specific behavior (not actually import something).

Consider a Moose-based class inheriting from a non-Moose base class. This happens, and often can work out fine. But what if that non-Moose base class needs an import list to configure some feature?

package Foo;
use Moose;
extends 'MyBase', ['-myfeature']; # An imaginary construct that not su
+rprisingly, doesn't work.
[download]

extends accepts multiple parent classes, so extends 'MyBase', -myfeature; would blow up. Is there a solution that doesn't involve this?

package Foo;
use Moose;
use MyBase -myfeature;
our @ISA = qw(MyBase);
[download]