<p>Seems like it would be a better experience for <code>go build</code> to fetch missing packages.</p>
<hr/>**评论:**<br/><br/>The_Sly_Marbo: <pre><p>I strongly disagree. I don't want <code>build</code> to do any more than compile, or your build process will have hidden magic like your CI silently using different dependency versions from your developers.</p></pre>indil7: <pre><p>Good point!</p></pre>dlsniper: <pre><p>This makes operating / maintaining the compiler a lot more simple. The compiler doesn't need to be aware of how to get the source code, it just needs to have it in GOPATH.</p>
<p>Think of the case you would like to use your own fork/mirror of a package but the compiler sees the import statement and goes to fetch that package from the original location.</p></pre>
这是一个分享于 的资源,其中的信息可能已经有所发展或是发生改变。
入群交流(和以上内容无关):加入Go大咖交流群,或添加微信:liuxiaoyan-s 备注:入群;或加QQ群:692541889
0 回复
- 请尽量让自己的回复能够对别人有帮助
- 支持 Markdown 格式, **粗体**、~~删除线~~、
`单行代码`
- 支持 @ 本站用户;支持表情(输入 : 提示),见 Emoji cheat sheet
- 图片支持拖拽、截图粘贴等方式上传