3 ms·
Well, the problem is when you have a []interface{} that contains a lot of float64 mixed with other things. If the size of the slice is large, I don't think you
by skybrian 9y ago
Well, the problem is when you have a []interface{} that contains a lot of float64 mixed with other things. If the size of the slice is large, I don't think you can assume it's all cached.
- zaarn 9y agoIf the slice is large, it's less likely to be cached either way.
- skybrian 9y agoTrue, but there is also locality of reference (having everything in a contiguous block uses less cache than pointer-chasing) and garbage collection pressure. In principle, using NaN boxing or a similar technique to store non-floats, you should be able to store floats in an []interface{} as efficiently as in a []float64. Scripting languages do this, but not Go.