always require one argument for "reverse"
The "reverse" command had many levels of optional arguments: garble [garble flags] reverse [build flags] [package] [files] This was pretty confusing, and could easily lead to people running the command incorrectly: # note that output.txt isn't a Go package! garble reverse output.txt Moreover, it made the handling of Go build flags pretty confusing. Should the command below work? garble reverse -tags=mytag It also made it easy to not notice that one must supply the main package to properly reverse some text that it produced, like a panic message. With the package path being implicit, one could mistakenly provide the wrong package by running garble in a directory containing a different package. See #394.pull/398/head
parent
08ec70e9a9
commit
1682e8ee10
Loading…
Reference in New Issue