I’m currently reading Oreilly’s Learning XNA 4.0 and I’ve noticed that the author is prone to creating a struct value, such as Vector2 or Rectangle multiple times with no regard for performance.
For example, a SquareCollision() method, that checks the collision between two game entities creates two Rectangles every time it is called, instead of simply having each game entity hold its own Rectangle field and compare the fields without creating any more struct values.
I’ve seen this pattern many times in many places and that made me wonder:
Is the creation of struct values that negligible in C#?
Does this really fall under the micro-optimizations section?
Perhaps because my experience is mostly with Java, the concept of ValueTypes is strange to me, but it seems that recreating a value from a struct (and calling it’s constructor) multiple times seems like a giant waste of resources.
Creating a struct for brief use on the stack is very cheap, and is not much different to just setting local variables for all those values, but with componentisation. However, as part of the object it would be an additional duplicate of the same data per object.
Both approaches are valid, depending on the scenario. On the stack, however, there is no real resource cost. As part of an object, you’d want to make sure you weren’t duplicating data unnecessarily, as that would have actual cost.
If it were a property on an object, you’d need to copy it lots of times.
If it were a field on an object, yes: it could be used in-place without ever copying, but: this is relatively small in most cases.
As always, you’d need to profile to know if it mattered.