4 ms·
Magic directory names seems a bit of a hack to avoid supporting this notion in the language itself. AFAIK this also introduces the English language into the cu
by frou_dh 12y ago
Magic directory names seems a bit of a hack to avoid supporting this notion in the language itself.
AFAIK this also introduces the English language into the currently freeform world of user import paths. I guess source files themselves already have something similar with the "_test.go" suffix, so there's some consistency with that.
- bwooce 12y agoWhat magic directory names? The special case for "pkg" is the only one I saw. The main proposal is one of scoping by directory hierarchy - /a/b/c can import a/b/d but a/g/x can't.
- frou_dh 12y ago> /a/b/c can import a/b/d but a/g/x can't. No - x can import d because d isn't in a directory literally named internal. That's the magic name.
- lloeki 12y ago> What magic directory names? "internal" > The main proposal is one of scoping by directory hierarchy - /a/b/c can import a/b/d but a/g/x can't. /a/b/c can import a/b/d, and /a/g/x and /z can too. The new rule is that /a/g/x can not import /a/internal/y.
- sltkr 12y ago> The new rule is that /a/g/x can not import /a/internal/y. As I understand it, /a/g/x CAN import /a/internal/y, because /a/g/x is in the directory tree that starts at /a/. However, /b/h/z CANNOT import /a/internal/y/ (while previously, it could).
- sambeau 12y agoPlus, every keyword is already in English.
- frou_dh 12y agoThat goes without saying at this point. I'm not saying the English-in-path thing is a huge deal, but it's worth noting effects that sneak in along with a feature.