On Wednesday, March 3, 2021 at 6:11:38 PM UTC-5 axel.wa...@googlemail.com wrote:
> On Thu, Mar 4, 2021 at 12:02 AM Michael Ellis <michael...@gmail.com> > wrote: > >> What's the right way to handle this use case? >> > > I think the right way to handle it is to modify the file. In the final > code, the import path should unambiguously point to where the code can be > found - regardless of whether it was using your skeleton to get started. > You might write a tool to do that modification automatically, if you want > to simplify things. > Thanks even though it's not the answer I was hoping for. Seems to me that since the Go Authors have accorded special status to directories named "internal" the module mechanism should recognize references to it and not require a globally unique path string. -- 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 https://groups.google.com/d/msgid/golang-nuts/63067d97-1aa3-4efb-92af-7ea0f831a873n%40googlegroups.com.
