Imagine you have a car and it runs faster than other cars and needs less gasoline, but due to historical reasons the steering wheel is made of barbed wire, there's 8 different accelerator pedals for different streets, pushing the wrong one may lead to a crash, and instead of a driver's seat there's a huge wooden dildo sticking out of the floor.

This is, in a nutshell, what using the C++ type system feels like.

Can't imagine because TÜV

@Alice OMG I'd love to see a TÜV certification for programming languages. Germans, please make that happen!

Yup. That’s an accurate description.

One of the 8 pedals is actually a foot gun.

@DirtEffect they do certify software tools like compilers, because of course they do. How else could they certify a system that is software controlled?

What's wrong with the type system?

@Lensflare Made me laugh out loud :)

@retoor It is attempting to combine expressivity, performance, and downward compatibility. This is a worthy goal in principle, but since compatiblity is a must and performance its main selling point, the expressivity suffers and suffers greatly.

Take the rvalue reference args for instance:

void foo(A &&v); //Matches only rvalues

template<typename T>

void foo (A<T> &&v); // Matches only rvalues

template<typename T>

void foo (T &&v);

// Matches fucking anything from values, through pointers to Bjarne Stroustrup's balls.

@retoor Or take polymorphism with strings:

void foo(const std::string &name);

void foo (int i);

...

foo("Hello world!");

Wanna guess which overload is called?

Of course its the int, because it is easier to convert a const char * to int than to std::string

Last example is sick