sub EXPORT loaded inside precompiled module doesn't seem to be run

[zoffixznet]

This looks very related to #1369

I modify a lexical in sub EXPORT:

$ cat Foo.pm6 
my $meow;
sub EXPORT ($conf = 'config.json') {
    dd $conf;
    $meow = $conf;
    { '&jconf' => &jconf }
}
sub jconf { say $meow }

And I load this module inside another module and export another routine that calls the routine from the first module that prints that lexical:

$ cat Bar.pm6 
use Foo 'bar.json';
sub meows is export { jconf }

I then load both modules, with the 'Bar.pm6' loaded second, yet when I use the routines to dump the lexical, I get only the value from the module that got loaded first and the dd that Bar.pm6 would've run doesn't get run:

$ perl6 -I. -MFoo -MBar -e 'jconf; meows'
Str $conf = "config.json"
config.json
config.json

But, if I stick no precompilation into Bar.pm6, then it works fine and the routines dump the value set by Bar.pm6's loading:

$ perl6 -I. -MFoo -MBar -e 'jconf; meows'
Str $conf = "config.json"
Str $conf = "bar.json"
bar.json
bar.json

$ perl6 -v
This is Rakudo version 2017.12-11-g2a8287c built on MoarVM version 2017.12-1-g912f967
implementing Perl 6.c.

[zoffixznet]

EDIT: just now noticed the dd doesn't get run the second time in the precompiled version, so looks like sub EXPORT doesn't even get run at all

[jnthn]

This is correct behavior. A use (also import, which use uses) is a compile-time operation. When the using module is precompiled, then the results of the import are serialized, so that the import, symbol table merging, etc. do not need to be repeated every single load time. Thus there is no import per module load and, as such, no IMPORT sub call per module load either.

[zoffixznet]

Thanks.