4 ms·
> inadvertent copy constructor/assignment operator calls This is much less of a problem (and much more controllable!) now that we have move semantics. > autom
by mrkline 10y ago
> inadvertent copy constructor/assignment operator calls
This is much less of a problem (and much more controllable!) now that we have move semantics.
> automatic memory allocs
It's hard to accidentally allocate memory if you don't have a system allocator hooked up.
> heavy-weight operator overloads
No more heavy-weight than a standard function call, and usually inlined at that.