3 ms·
I know it's a convention since the inception of the language, but the operator overload abuse of the bitshift operator still makes me sad every time I see it :(
by connicpu 2y ago
I know it's a convention since the inception of the language, but the operator overload abuse of the bitshift operator still makes me sad every time I see it :(
- Chaosvex 2y agoOn the plus side, it's optional. The same thing can be achieved with put()/get() equivalents.
- bluGill 2y agoYou are not alone. many on the standard committee are trying to get rid of it. std::print is the new way to do io instead of cout in part so you don't have to abuse shift for io. This is new in c++23 though so few people know about it. Bjarne appears to prefer cout though, so it isn't universal.
- soursoup 2y agoDanish Bjarne may have his < right next to lshift. He needs to use shift+. to enter colon. On US layout colon is a single keypress but < is shift+. This may explain the discrepancy. —- from someone who read Bjarne at 16yo. All hail the Bjarne
- mhuffman 2y ago>operator overload abuse Array programming languages smugly enter the chat
- deleted 2y ago[deleted]