cm0002@lemmy.world to Programmer Humor · 22 days agoTell me the truth ...piefed.jeena.netimagemessage-square168linkfedilinkarrow-up11.18Karrow-down117
arrow-up11.17Karrow-down1imageTell me the truth ...piefed.jeena.netcm0002@lemmy.world to Programmer Humor · 22 days agomessage-square168linkfedilink
minus-squaretimhhlinkfedilinkarrow-up24·21 days agoWell there are containers that store booleans in single bits (e.g. std::vector<bool> - which was famously a big mistake). But in the general case you don’t want that because it would be slower.
minus-squareethancedwards8linkfedilinkEnglisharrow-up7·21 days agoWhy is this a big mistake? I’m not a c++ person
minus-squarebitcrafterlinkfedilinkarrow-up5·21 days agoThe mistake was that they created a type that behaves like an array in every case except for bool, for which they created a special magical version that behaves just subtly different enough that it can break things in confusing ways.
minus-squareethancedwards8linkfedilinkEnglisharrow-up3arrow-down1·21 days agoCould you provide an example?
minus-squaretimhhlinkfedilinkarrow-up1·17 days agoThe biggest problem is that each element doesn’t have a unique memory address; iterators aren’t just pointers.
Well there are containers that store booleans in single bits (e.g.
std::vector<bool>- which was famously a big mistake).But in the general case you don’t want that because it would be slower.
Why is this a big mistake? I’m not a c++ person
The mistake was that they created a type that behaves like an array in every case except for
bool, for which they created a special magical version that behaves just subtly different enough that it can break things in confusing ways.Could you provide an example?
The biggest problem is that each element doesn’t have a unique memory address; iterators aren’t just pointers.