<p>This is in <code>pool.go</code>. Originally I was trying to understand how pool.get worked. It brought me down a rabbit hole and I ran into this</p>
<pre><code>func indexLocal(l unsafe.Pointer, i int) *poolLocal {
return &(*[1000000]poolLocal)(l)[i]
}
</code></pre>
<p>What is it doing? initializing an array of size 1000000 of poolLocal. and then ... ?</p>
<hr/>**评论:**<br/><br/>hlidotbe: <pre><p>Someone correct me but if I read that correctly it:</p>
<ul>
<li>"cast" <code>l</code> to a pointer to an array of 1000000 pool local (I guess since it's an unsafe pointer the compiler is OK with that)</li>
<li>returns the address of the pool local item at index <code>i</code></li>
</ul>
<p>The large array size is to avoid tripping whatever boundary check the compiler is inserting I assume. There's no actual array of that size. </p></pre>lems2: <pre><p>ty!</p></pre>itsmontoya: <pre><p>You nailed it. One thing to note, this code is changing very soon. If you check tip, they recently improved pool performance.</p></pre>
这是一个分享于 的资源,其中的信息可能已经有所发展或是发生改变。
入群交流(和以上内容无关):加入Go大咖交流群,或添加微信:liuxiaoyan-s 备注:入群;或加QQ群:692541889
0 回复
- 请尽量让自己的回复能够对别人有帮助
- 支持 Markdown 格式, **粗体**、~~删除线~~、
`单行代码`
- 支持 @ 本站用户;支持表情(输入 : 提示),见 Emoji cheat sheet
- 图片支持拖拽、截图粘贴等方式上传