What version of Go are you using (go version)?

$ go version
go version go1.20.3 linux/amd64

Does this issue reproduce with the latest release?

Yes

What operating system and processor architecture are you using (go env)?

N/A, applies to any GOOS/GOARCH

What did you do?

In a Bazel build action running in a symlink-based sandbox, try to build the Go standard library or any third-party package using //go:embed.

What did you expect to see?

The build passes just as it would if the input files weren't symlinks. Tools only play nice with Bazel if they follow symlinks, as whether or not an input file to a Bazel build action is a symlink depends on the particular strategy with which Bazel chooses to execute the action (e.g. remotely or locally, in a sandbox or not, ...).

//go:embed not allowing symlinks to be embedded makes sense and I am not asking for that to be changed. However, it would be very helpful if it could be made to follow symlinks, either by default or optionally, guarded by a flag or environment variable.

What did you see instead?

external/go_sdk/src/crypto/elliptic/p256_asm.go:24:12: pattern p256_asm_table.bin: cannot embed irregular file p256_asm_table.bin

This happens because of the use of Lstat in

This issue requires rules_go to copy around the stdlib and breaks build actions that operate on generated code.