Sq::Exporter

[DavidRaab]

use Sq::Type; # import defaults

use Sq::Type {
    import => [qw/t_run t_valid/],   # exports single requested functions
    into   => 'Package',
    as     => {t_run => 'type_run'}, # exports single function under new name
    sig    => 1,                     # load default signature
    sig    => 'Sig::Whatever',       # loads signature file once before exporting
    prefix => 'type_',               # another prefix
};

# same
use Sq::Type qw(t_run t_valid); 
use Sq::Type {
    import => [qw/t_run t_valid/],
}

defining another signature opens up some questions. First of, a signature file should only be loaded once. What happens when multiple use Sq::Type are in your project with different signatures?

Then only the first one would be loaded.

A better approach. Don't add signatures to the original package. First load/import functions. Then add signatures to the imported functions in the target package. This way you can load/import a module with different signatures at different places. While this is a cool feature. This isn't so important at the moment.

[DavidRaab]

use Sq::Type {
    extra => ['Sq::Type::Logging'],
};

The signature works by replacing installed functions and wrapping them into a new function that has type-checking
added. Another example in Perl is the Memoize module that adds caching to a function. This technique can be
used for a lot of things.

The idea is that extra can load additional AOP modules. Here the same problem as sig => 'Sig::Whatever' arises. Should those modules be loaded in the original package, or just to the exported functions? Usually exported functions make more sense.

This is a feauture/idea for the future.