3 ms·
Hence “blindly”. The blog post was a detailed, less sanctimonious version of your comment.
by pdpi 6y ago
Hence “blindly”. The blog post was a detailed, less sanctimonious version of your comment.
- TonyTrapp 6y agoBut then you could write a blog post about pretty much every API misuse ever, which doesn't really seem very constructive to me. But okay, maybe it's more obvious when having worked with pre-C++11 code, where you would have killed for something like emplace_back. If you are new to the language and only know modern C++, you probably don't think much about why emplace_back exists in addition to push_back, and why it can be faster.
- xKingfisher 6y agoGiven the whole scanf/strlen thing going on, more blog posts about API pitfalls wouldn't necessarily be a bad thing. And that is basically the premise of the Abseil Tip of the week series, which are an incredible resource for learning how to work with modern C++.
- pjmlp 6y agoGiven that some schools still teach C++ with Turbo C++ for MS-DOS, one cannot expect that everyone is up to date with CppCon C++Now talks.
- IshKebab 6y agoYeah but the title sounds like "you shouldn't just always use emplace_back instead of push_back" but the actual content is "you shouldn't use emplace_back completely incorrectly because you don't know what it is". The only actual argument against blindly using emplace_back everywhere is that it has worse compile time in a deliberately pathological microbenchmark. Not convincing, though it is interesting.