Why the fuck does everything in C++ insist on endlessly copying shit here and there, spawning 4 (FOUR!!!) copies of some fucking object during certain calls to methods of stdlib containers (vector, tuple etc).
I can't create a fucking thread without it copying my ``functor'' object (with operator()) at least twice for some fucking reason.
So yeah, if you want fast C++ programs, you fucking write them in C, with manual handling of pointers and shit. Fuck C++.
Name:
L. A. Calculus!!wKyoNUUHDOmjW7I2013-06-16 0:23
>>43
I STOLE PHYSICAL COPIES FROM DA ISO BACK IN DA DAY. DONT GOT NO ELECTRONIC COPIES, BUT U CAN GET DA DRAFTS EASY AS SHIT IF YOU LOOK AROUND. IT'S DA SAME SHIT ANYWAY, SO WHO GIVES A FUCK.
Name:
Anonymous2013-06-17 14:31
We have a guy that demands that we write out every trivial detail of copying this or that or marking this or that as const as if it improves the quality of our software. We have to do that because the guy is the butt-shoving prostate massager, I mean, byte-saving project manager
When you have "automatic" memory management but no GC, you have to make copies. You could try reference counting, but it doesn't work with cycles.
Name:
Anonymous2013-08-27 15:15
How are you measuring this ``copying''?
If you're putting a print statement in your copy constructor then it's no surprise it's forced to call it since you made it have side effects.