Nice work! I remember getting similarly substantial speed-ups by pre-sizing my collections to the maximum size they'd need to be, since on large problem instances the overhead of re-allocating them as they grew was noticeable.

For me I was working in C#, so allocating new large collection sizes was probably triggering a full garbage collection sweep and compaction in the middle of the hot loop. 😖

Hm! Luau does indeed look interesting!

I think it's valid to post here about bugs encountered in tools. There might be known community workarounds that are faster to implement than waiting on the bug report pipeline to do something about it. I just like to remind people to also report the bug in case their question here yields no such known fix.

You might have a better experience using bug trackers than I have. 😉

But the question isn't "what is this bug" the question is "what do I do about this problem" whether it's a bug or not.

Vectorization... In terms of ecs i always hear vectorization and cache friendliness. Those are two different things, right ? Is vectorization of loops where we acess structs even possible in c# ? I actually could only find stuff about c# vectorization of primitives like ints, float, doubles.

@Tyyppi_77 We can fix that with an edit if it's bothersome.

If StackExchange meant for only the original poster to edit questions to make improvements, we wouldn't have an edit button too. But we do. 😉

There we go, does that read a bit better now?

And they offer both because, it turns out to run a useful community site, you need both. Relying on help documentation alone doesn't solve the problem.

@Tyyppi_77 I made a similar argument when we discussed low-effort questions on Meta some years ago.

Kind of accepting that it's what I signed up for when becoming a regular commentor/editor/moderator here. 😉

haha yeah comes with the territory