Alternative to Julia's include() for shared imports in a multi-file module?

[timi5691]

Hi,

For example:

// file_a.v
module md_unit

import structs
import md_grid

// file_b.v
module md_unit

fn state_idle(...) {
    // uses structs and md_grid
}

Currently, each file must repeat its own import statements even when all files belong to the same module.

Is there a recommended way in V to avoid repeating imports across files of the same module?

Something similar to Julia's include() behavior, or a module-level import shared by all files?

If not, is there a design reason why imports are intentionally file-scoped rather than module-scoped?

Thanks.

[medvednikov]

Both Go and V do this by design.

Imports are dependencies of a file, not magical state of the whole module.

It makes each file self-describing. When you open file_b.v, you can immediately see what external modules it depends on. You don't have to hunt for a central imports file and wonder which imports are available by side effect.

It improves readability, tooling, refactoring, dependency analysis, and compile determinism. The cost is repetition.

vfmt/gofmt take care of this automatically.