Binding list to variable with `@' sigil doesn't survive export/import

[paulprocacci]

The Problem

unit module Module::Something;

our @Locations is export := ('yabba', 'dabba');

+-------------------------------+
use Module::Something;

say @locations.WHAT;

Expected Behavior

I would expect a list to survive this import/export.

Actual Behavior

I end up with an array instead of a list.

Now, admittedly this may be intended but I cannot find a reasonable explanation for this in the documentation. It may exist and I may have missed it. I understand I can use a different sigil; I tested that and that works without issue, but I can't fathom why this specific example doesn't.

[2colours]

It would be nice to get actual golfed, reproducible issues so that there don't need to be extra laps run only to analyze the behavior. In this case: some actual folder structure. Also for this example - if the issue is indeed import/export - our wouldn't be needed and that strikes me as something that might interfere...

[lizmat]

I think it's a bug in the handling of our exports.

The following DWIM:

sub EXPORT() {
    Map.new: '@Locations' => <yabba dabba>
}