On Thursday, March 4, 2021 at 10:14:03 AM UTC-5 [email protected] wrote:
> On Thu, Mar 4, 2021 at 3:54 PM Michael Ellis <[email protected]> wrote: > >> Not sure if my case is all that special. Seems like the requirement for >> a full path to an internal package breaks the concept of "internal" because >> it gives everyone import access to whatever the internal package exports. >> > > Really? I can't reproduce that. If I create a minimal module importing " > github.com/Merovius/srvfb/internal/fb" and try to build that, I get an > error message: > > foo.go:3:8: use of internal package github.com/Merovius/srvfb/internal/fb > not allowed > > So, the internal mechanism seems to work just fine, to me? Note that > "every importer needs to mention the full path" is not the same as > "everyone mentioning the full path can import". > My bad. I should have tested before writing that. Thanks for checking. Good to know the tools are enforcing the distinction. Still, the import path requirement does get in the way of being able to create a new application by cloning and revising an existing one without doing a recursive sed (or equivalent thereof). -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/35e46b0e-a730-4b27-9ca0-313ddfccf855n%40googlegroups.com.
