"too many Go files" when importing 2+ files in a subpackage

[SolarLune]

Hello~

I believe it's documented that scriggo.BuildProgram() only can handle one file at the base level of a filesystem. However, I'm finding that this is also the case for all sub packages imported by the main module in descendant directories and built with scriggo.BuildProgram(), which feels a bit tough to work around; not sure if it's a bug?

As an example, here's my layout for the file system being loaded and built with scriggo:

scripts/go.mod - The go.mod file declaring the module being imported
scripts/main.go - Calls `import _ "scripts/gameobjects"`
scripts/gameobjects/player.go
scripts/gameobjects/player2.go -- This second file breaks scriggo's build function

And here's a simple test case:

tooManyGoFilesSubPackages.zip

Maybe this is an extension of issue #521? Maybe because scriggo is internally changing all modules' names to main and executing them, which triggers the "too many Go files" error, even if they are not at the root of the file system?

[gazerro]

You are right, this is quite inconvenient to work around.

At the moment this is a limitation of the current compiler, more than a bug. Right now it still assumes one ".go" file per package, so subpackages with multiple ".go" files are not handled like they are in the standard Go compiler.

It is something that can be improved, but it requires a wider internal change, so it is not an immediate fix.