Hidden allocations when using vararg and spread operator

[b005t3r]

Thanks for the responses, guys. I need to start using this bytecode viewer

@ilya.gorbunov

It might be possible for the compiler to optimize such copying away, for example when one vararg function passes its array to another vararg function and doesn’t use it itself after, however such optimization has not been baked yet.

Exactly. It looks like there’s currently no way to modify elements of array passed as vararg, so such optimization should be pretty safe.