Hi, Not recommended, it's better to be explicit by using the full import path, even if it feels odd at first, other users reading your code will know exactly where the packages are. For more info, see the last two replies here
https://groups.google.com/d/topic/golang-nuts/8grbqER8h54/discussion from a few days ago. Thanks On Wednesday, February 22, 2017 at 11:52:08 AM UTC-5, so.q...@gmail.com wrote: > > Is it recommended or acceptable to use relative import paths, particularly > for nested packages? or should I typically always use the full path? > -- 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.
