--export=all exports the module's variables, not a function's locals

[ASDAlexander77]

With --export=all (or any --export filter matching a local's name), a library's __decls declared every local variable of every function, method and accessor as a @dllimport global, in a .f_<function> namespace:

namespace .f_Node.get_total {
@dllimport
let t : s32;
}
namespace .f_f {
@dllimport
let w : s32;
}

No library defines those symbols. I found this in #391's investigation.

Cause: in mlirGen(VariableDeclarationList), the filters (getExportModifier) were applied to every variable statement, function bodies included. export can't be written inside a function, so only a filter could mark a local, and it did.

Fix: the filters apply only where there's no function (!genContext.funcOp), which means the module and its namespaces. Line 965 of the same function already uses that test to mean "module level". A module-level variable is still exported under --export=all, and a namespace's export const still is.

Test: test-compile-export-all-no-locals compiles export-all/locals.ts (a getter, a method and a function with locals, plus a module-level let) with --export=all --emit=mlir. It must show let moduleLevel and no namespace .f_. It fails without the fix.

Results: the suite passes locally, 3012/3012. DefaultLib builds with --export=none, so it's unaffected.

🤖 Generated with Claude Code