Sometimes I see code that uses a new allocation to set a Unity Vector2/3 with new values instead of Set(), unless I'm missing some setting of the compiler magically replacing that instruction with something else this is a very unoptimized way of doing so.
@djlink but... Vector3 is a struct, so it should be allocated on the stack and not make a difference because the values are just overweritten anyways?
I'd really try benchmarking those two, I'd bet there's no difference.
