Skip to content
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/go: documentation unclear with argument parsing for go tool #5566

Closed
gopherbot opened this issue May 27, 2013 · 4 comments
Closed

cmd/go: documentation unclear with argument parsing for go tool #5566

gopherbot opened this issue May 27, 2013 · 4 comments

Comments

@gopherbot
Copy link

by elazarl:

In http://tip.golang.org/cmd/go/#Test_packages the last argument to the test command is
flags to test binaries. It is unclear how to disambiguate package names from test flags
(if you disambiguate by having hyphen - it should be clearly spelled out).

Similar issue arises for go run, with packages ending with ".go".
Documentation should clearly spell out that go arguments are stopped being parsed as go
files after the first argument not ending with ".go".

(I'm not saying Go should support weird package names or arguments with ".go"
suffix, but the rules for argument parsing should be spelled out clearly in the docs.)
@robpike
Copy link
Contributor

robpike commented May 28, 2013

Comment 1:

Labels changed: added priority-soon, documentation, removed priority-triage.

Owner changed to @robpike.

Status changed to Accepted.

@robpike
Copy link
Contributor

robpike commented May 30, 2013

Comment 2:

Go run is well specified. Go test needs work and a CL is coming.

@gopherbot
Copy link
Author

Comment 3 by elazarl:

Even if go run is well specified. a small note like 'go files are files with ".go"
suffix' would help a lot to people like me who weren't sure how go files are defined.

@robpike
Copy link
Contributor

robpike commented Jun 3, 2013

Comment 4:

This issue was closed by revision 59fb90a.

Status changed to Fixed.

@golang golang locked and limited conversation to collaborators Jun 24, 2016
@rsc rsc unassigned robpike Jun 22, 2022
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants