> but that will be slower because it's a copy/a function call/an indirect branch/a channel send/a shared memory access I really dislike these takes. I see engi

> but that will be slower because it's a copy/a function call/an indirect branch/a channel send/a shared memory access I really dislike these takes. I see engineers optimize these cases and then go ahead and make two separate SQL queries that could be one, ruining any false optimization gains they got by lord know how many times. Yeah, you can loop over that 100 element list twice doing basic computation if you want, it's not going to make a difference for many engineering workloads, but could make a big difference in readability.