2018-02-20 13:02 GMT-08:00 David Anderson <d...@natulte.net>: > [snip] > > I also believe the tooling around vgo should encourage/make default this > behavior for binary modules (and maybe for library modules as well, though > that's less clear to me). The default behavior when writing Go programs > should be to use the latest of everything, unless you have a specific reason > to hold back. Among other things, that ensures you are patched against CVEs > and whatnot.
AIUI, that is the opposite of what minimum version selection does; active maintenance is required. This is at least no worse than any other case where you need to make a determination on whether to consume some library or tool based on whether it is actively maintained. And when the tools are maintained, seems like it is probably better. --dho -- 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. For more options, visit https://groups.google.com/d/optout.
