> > Waiting for Cross-Platform standardized SIMD vector datatypes
> We sort of have this? compiler loop vectorization is, effectively, this. Granted it's not standardized.
Auto-vectorization isn't remotely capable of what an engineer is capable of doing through intrinsics.
> > nonstandard extensions ... to run computations in parallel on many cores
> std::thread?
Compare that to the capabilities provided by Thread Building Blocks.
http://www.open-std.org/JTC1/SC22/WG21/docs/papers/2013/n355...
Look how many people are complaining on here about how complicated c++ is. If something like tbb was integrated they would be all over it.
They probably meant something more declarative, along the lines of OpenMP.
Most STL algorithms can be executed in parallel from C++17.
> Waiting for Cross-Platform standardized SIMD vector datatypes
We sort of have this? compiler loop vectorization is, effectively, this. Granted it's not standardized.
> nonstandard extensions ... to run computations in parallel on many cores
std::thread?
> Debugging cross-platform code using couts, cerrs and printfs
True, but i think this is not the language's fault. C/C++ debugging tools are great (the best?).
Debugging any sort of meta-programming is a mess; would definitely agree w/ that. hopefully concepts will help.
> Forced to use boost for even quite elementary operations on std::strings.
This one i agree with.