[rao-v]

I was thinking about just asking the compiler to do the expensive reshuffle when I need it to, but you could go further and expect the compiler to figure out the likely access pattern and spend the transformation budget.

Heck memory is cheap (fine was cheap) give me a data structure that amortizes writes cleverly by maintaining both SoA and AoS at the same time

[jayd16]

Well the whole point is that memory (cache in this case) is not cheap at all. We have very little and the point is to do as little loading of what you don't care about as possible to keep the cache full of only exactly what is needed for the task.

How do you imagine it's possible to write to every SoA and every AoS and have that as cheap as only the first step?

[rao-v]

Many operations are map reduce where writes are low volume compared to reads