Relative package don't need to be searched for, they are explicit (indicated with ./ or ../)
Then it seems to be: 1. vendor tree, if it exists 2. GOROOT 3. GOPATH, from left to right Trying to build a package with an import that cannot be found will display an error listing all the locations it looked for the package. To get the vendor tree listed, a vendor directory must exist in the package you are trying to build. On Tuesday, February 21, 2017 at 3:01:59 AM UTC+1, so.q...@gmail.com wrote: > > What is the search order for the import path? > for example, relative then vendor then workspace? > > > -- 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.
