External access to Internal package in workspace

[okm-8]

Go version

go version go1.23.3 darwin/arm64

Output of go env in your module/workspace:

GO111MODULE='on'
GOARCH='arm64'
GOBIN=''
GOCACHE='~/Library/Caches/go-build'
GOENV='~/Library/Application Support/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='arm64'
GOHOSTOS='darwin'
GOINSECURE=''
GOMODCACHE='~/go/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='darwin'
GOPATH='~/go'
GOPRIVATE=''
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/opt/homebrew/opt/go/libexec'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='local'
GOTOOLDIR='/opt/homebrew/opt/go/libexec/pkg/tool/darwin_arm64'
GOVCS=''
GOVERSION='go1.23.3'
GODEBUG=''
GOTELEMETRY='local'
GOTELEMETRYDIR='~/Library/Application Support/go/telemetry'
GCCGO='gccgo'
GOARM64='v8.0'
AR='ar'
CC='cc'
CXX='c++'
CGO_ENABLED='1'
GOMOD='/dev/null'
GOWORK='~/projects/sandbox/go_internal_package_issue/go.work'
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -arch arm64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -ffile-prefix-map=/var/folders/xk/mlc_37qd2jj8pcjkmsf9gqb40000gn/T/go-build302425133=/tmp/go-build -gno-record-gcc-switches -fno-common'

What did you do?

We made some project

.
├── go.work
├── module-a
│   ├── go.mod
│   └── internal
│       └── test.go
└── module-b
    ├── cmd
    │   └── main.go
    └── go.mod

I am not going to deep, but by coincidence we get

// module-a/go.mod

module moduleA

go 1.23

// module-b/go.mod

module moduleA/moduleB

go 1.23

so module B contains moduleA as part of its path in workspace

and, than, we do that

// module-b/cmd/main.go

package main

import "moduleA/internal"

func main() {
	internal.Test()
}

What did you see happen?

All is compiling and working

What did you expect to see?

Should not even compiling, because moduleB is trying to call an internal function of moduleA

[gabyhelp]

Related Issues

• cmd/go: can't use internal package in a module #27022 (closed)
• cmd/go/internal/modload: `MainModuleSet.DirImportPath` does not check module boundaries #66119
• cmd/go: internal package is importable to the packages which is not rooted in the same subtree. #12217 (closed)
• cmd/go: modules: exposure of internal packages #30569 (closed)
• cmd/go: clarify go.mod documentation for trivial relative modules #27274 (closed)
• cmd/go: improve error when a package exists in the filesystem but is in a different module #30590 (closed)
• cmd/go: go work causes go build to error when symlinks are involved #53343
• cmd/go: document 'internal' package visibility for module mode #38579
• Add support for short import paths for packages in the same module #41568 (closed)
• cmd/go: 'go test' with a file argument in a module root uses the wrong import path #28011 (closed)

_{(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)}

[mvdan]

Duplicate of #30569.