/ go Public
cmd/go: diagnose platform-specific identifiers when building for other platforms #26967
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
What version of Go are you using (
go version go1.10.3 darwin/amd64
Does this issue reproduce with the latest release?
What did you do?
Execute this command to get the error below:
What did you expect to see?
What did you see instead?
When a colleague that had not used golang previously tried to compile some linux-specific project on OSX, they got the 'undefined' error above and assumed the project was simply broken, not that it was platform-specific. If the golang compiler gave this user a better error message, they most likely would have figured out their issue quicker.
It seems to me that when the compiler runs into an undefined function/constant/whatever, it would be really useful if it could look at the other platform-specific files in that directory and see if they are defined there. If so, it could emit a better error message noting that the function isn't defined for the particular platform that you're compiling for, but that it is defined for other platforms (and mention which ones).
Thinking about my imagined solution, when encountering this type of error the compiler could probably 'quickly' scan the AST of other platforms and see if the thing was defined there? In particular, since this would only be done on error, that wouldn't affect compile performance in general?
Thanks for your consideration.
The text was updated successfully, but these errors were encountered: