go: potential for mismatch between package name and output directory

[asteurer]

Consider the following command:

wit-bindgen go -w wrld --out-dir baz --mod-name github.com/foo/bar/baz ./wit

The package name wit_component contained in the generated baz/wit_bindings.go and the output directory baz won't match and cause package errors.

I see two possible ways to view this:

1. This is acceptable behavior and just needs to be documented
2. This is not acceptable behavior and we need to update the logic on this line.

@dicej Eager to hear your thoughts!

[dicej]

I guess it comes down to how the --mod-name parameter is intended to be used. I'll admit I didn't fully understand why the wit_component name was hard-coded at the line you referenced, regardless of the value specified via --mod-name.

[dicej]

Another question to ponder: Considering that the wit_bindings.go file in question does not contain any public symbols, under what circumstances would the user import that package? Its current sole purpose is to declare the //go:wasmexport functions corresponding to any and all exports defined in the target world.

The use case presented for the --mod-name option in #1494 was SDKs. Are you imagining an SDK might contain exported functions as well as imported ones? If so, how might that work? If not, then we might want to skip emitting that wit_bindings.go file entirely when --mod-name is specified, and perhaps raise an error if the target world contains exports.