Re: [go-nuts] Avoid forcing my module users' to carry dependencies from code that live under the same repo just as examples/ debugging purposes.

Indeed. Some parts of it are fine though, given that the ask was for a starting point. I agree completely with the pkg stuff being wrong. I use just some of the ideas here, but I don’t see what the point of pkg is. On Fri, Apr 14, 2023 at 16:04 'Dan Kortschak' via golang-nuts < golang-nuts@googleg

Re: [go-nuts] Avoid forcing my module users' to carry dependencies from code that live under the same repo just as examples/ debugging purposes.

On Fri, 2023-04-14 at 14:01 +0800, Jim Idle wrote: > You might start with this repo: > > https://github.com/golang-standards/project-layout > > This is not an 'official' standard, though it does encapsulate the > things that are standard go such as the internal directory.  > > Personally I avoid

Re: [go-nuts] Avoid forcing my module users' to carry dependencies from code that live under the same repo just as examples/ debugging purposes.

You might start with this repo: https://github.com/golang-standards/project-layout This is not an 'official' standard, though it does encapsulate the things that are standard go such as the internal directory. Personally I avoid its recommendation to use a directory 'pkg' to store your module co

[go-nuts] Avoid forcing my module users' to carry dependencies from code that live under the same repo just as examples/ debugging purposes.

I made a very simple module (the very first one that I uploaded to my GitHub account). I had a main.go file in the root directory used just for testing/debugging (and to keep as an example of how to use the module). Then I "go got" my module from another project just to see that this project transi