I have nothing to add to Sean's excellent reply, other than to mention... > Most of my experience has been with external tooling, and here I prefer using > `go install pkg@version` > over pinning with go.mod as this ensures no interference in dependency > versions between tools, > and can be put in the same place as the other scripting that makes use of the > tools.
There is also `go run pkg@version` which obviates setting PATH at the expense of slightly more command startup overhead. Regarding that overhead, on a recent tools call Michael Matloob from the cmd/go team mentioned they were looking into optimisations that might reduce the overhead of `go install pkg@version`. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CACoUkn5LFb9_QXmb69fErCvbuHzYssJpduvGWdMJd8H6kA_frQ%40mail.gmail.com.
