Any reason not to have a `utils_test.go` file - and puts your utilities in there? Seems like the simplest solution.
Then they only get included for your tests. Using /internal for testing tools feels a bit strange to me IMHO. Mark On 18 December 2016 at 11:13, Matt Harden <matt.har...@gmail.com> wrote: > An import of a path containing the element “internal” is disallowed if the > importing code is outside the tree rooted at the parent of the “internal” > directory. > > Note the use of the word "tree" in that sentence, as opposed to > "directory". > > On Sun, Dec 18, 2016 at 5:48 AM Henry <henry.adisuma...@gmail.com> wrote: > >> Where do you put this internal package in relation to the rest of the >> packages? Is it something like this: >> >> project/ >> package1/ >> package2/ >> package3/package4/ >> internal/testhelpers/ >> >> I thought internal package would only be visible to its immediate parent? >> I want it to be usable across the packages. >> >> Thanks. >> >> -- >> 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. >> > -- > 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. > -- T: http://www.twitter.com/neurotic W: www.compoundtheory.com -- 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.
