4 ms·
It's a bit silly that people fuss over go package path names. Any non-trivial app would use a preprocessor to manage the import lines. This problem was solved
by gowld 6y ago
It's a bit silly that people fuss over go package path names.
Any non-trivial app would use a preprocessor to manage the import lines.
This problem was solved 40 years ago.
- heavenlyblue 6y agoI think I just made an example of receiving a merge request somewhere on Github, where you don't have access to the preprocessor or are not running it yourself. It is easy to accept the change when the change looks so much like lines in other files. The issue was resolved by the comment on the same level, however your comment added 0 to the discussion.