-
Notifications
You must be signed in to change notification settings - Fork 17.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cmd/compile: inaccurate compiler error on duplicate wasmexport symbol #68982
Labels
compiler/runtime
Issues related to the Go compiler and/or runtime.
NeedsFix
The path to resolution is known, but the work has not been done.
Milestone
Comments
gopherbot
added
the
compiler/runtime
Issues related to the Go compiler and/or runtime.
label
Aug 21, 2024
CC @golang/wasm |
mknyszek
added
the
NeedsFix
The path to resolution is known, but the work has not been done.
label
Aug 21, 2024
It seems to me this is unfortunate.
Could we simply use the wrapped function position for wrapper ones instead of auto generated? cc @cherrymui |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
compiler/runtime
Issues related to the Go compiler and/or runtime.
NeedsFix
The path to resolution is known, but the work has not been done.
Go version
tip
Output of
go env
in your module/workspace:What did you do?
I created a package that exported two identical symbols (in the same package) using the go:wasmexport compiler directive.
What did you see happen?
I saw a compiler error:
What did you expect to see?
The error message should be able to point to the line number of both symbols:
It is also notable that
main.go:5
is the location of the return, not the compiler directive.The text was updated successfully, but these errors were encountered: