I'm looking at what I should do to keep my packages current with respect to 
modules.  The tutorials have covered top-level packages, but I haven't seen 
any discussions around low-level packages.  In particular, I have some 
low-level packages that rely only on the standard library.  It's not clear 
whether or not these packages should have a go.mod file.  At most, it would 
specify the minimum version of go.  I don't see much impact on usability or 
maintenance either way.

For vendoring, it was best practice (?) that only top-level packages would 
vendor.  I'm wondering if this rule applies to modules.


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 

Reply via email to