> On Sun, Dec 24, 2017 at 12:31 AM Mariusz Gronczewski <xani...@gmail.com> wrote:
> Because other languages do not force you to have name of the package be derivative of the repo name. Neither does Go. The whole tool chain uses the name in the package clause, the import path is used solely to locate the package directory, it is never used to determine the package name. > That's the cost of having import statement be able to accept "just a path to a thing in the internet" (which is reasonable imo) Same comment applies here. The repository at github.com/user/bar can be package bar just fine. It'll simply be always what's written in the package clause, unrelated to the import path. -- -j -- 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.
