You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
We've had confused users a handful of times by now. And it's reasonable to expect flags to be after the command, as that's how flags work for cmd/go itself. I don't think we want to mix our flags with Go's, or start accepting flags in either place. Both seem like worse solutions long-term, as they can add confusion. However, we can quickly give a useful hint when a flag is misplaced. That should get new users unblocked without asking for help. We use a regular expression for this purpose, because it doesn't seem like a FlagSet supports what we need; to detect whether an argument is one of our flags, without actually applying its value to the flagset. Our flagset would also error on Go's flags, which we don't want. |
3 years ago | |
---|---|---|
.. | ||
asm.txt | 3 years ago | |
basic.txt | 3 years ago | |
cgo.txt | 3 years ago | |
crossbuild.txt | 3 years ago | |
debugdir.txt | 3 years ago | |
embed.txt | 3 years ago | |
gogarble.txt | 3 years ago | |
goversion.txt | 4 years ago | |
help.txt | 3 years ago | |
implement.txt | 3 years ago | |
imports.txt | 3 years ago | |
init.txt | 4 years ago | |
ldflags.txt | 3 years ago | |
linkname.txt | 3 years ago | |
literals.txt | 3 years ago | |
modinfo.txt | 3 years ago | |
plugin.txt | 3 years ago | |
position.txt | 3 years ago | |
reflect.txt | 3 years ago | |
reverse.txt | 3 years ago | |
runtime-related.txt | 4 years ago | |
seed.txt | 3 years ago | |
syntax.txt | 3 years ago | |
test.txt | 4 years ago | |
tiny.txt | 3 years ago |