As he says, it makes the (compiled) code smaller, which often means faster since more stuff fits in the instruction cache. Though in this case I guess he could just have it be the last thing in the function since both branches go there anyway. (Edit: nah, I thought of it wrong -- it can't just go in the end.)
This guy is fantastic. Seriously one of my favorite people to watch.
My favorite C++ guy
CPP MAN
@@notinlist He's actually D MAN
you should always code your c++ 11 and c++ 14 keeping in mind how many electrons are moved down the copper wires you know...
A 5% difference in performance translates to 5% more battery life. That's huge.
5% difference in core of language or popular libraries is like you know eliminating few data centers. Billions of dollars worth.
How does putting reference count at the start of the class help?
To anyone who is against using goto, do recall what the underlying assembly looks like.
Well, on current Clang and GCC (in 2021) using `goto` and using two `delete`s produce same code.
i don't understand, why we need goto? Why not just dublicate "delete p_;" instead of goto?
As he says, it makes the (compiled) code smaller, which often means faster since more stuff fits in the instruction cache. Though in this case I guess he could just have it be the last thing in the function since both branches go there anyway. (Edit: nah, I thought of it wrong -- it can't just go in the end.)
ZII is really powerful
If one is prematurely optimizing one is not allowing the compiler to know better.