iostream

My understanding is that the main motivation behind the introduction of iostream was to make a type-safe variant of printf.

String literals should be (const) basic_strings, and there should be no way to access stdio's horribly-easy-to-buffer-overflow machinations now that there's iostream.

C++ <iostream> overloads the bitshift operator and nobody seems to mind.

See for example the iostream operators << and >> in C++, which actually have a very awkward precedence that forces you to parenthesize things in unexpected ways sometimes.

Here's idiomatic hello world, with <iostream> vs.

Merely including <iostream> results in std::cout/std::cerr/std::cin being constructed on startup even if they're never used (as in this case).

* Subsets avoiding the use of <iostream>.

#include <iostream> using namespace std; int foo(int&& i){ return i; } template<class T> T bar(T&& i){ return i; } int main() { int i=0; cout << foo(i) << endl; return 0; } edit: I am replying humbly.

This seems to be the equivalent to someone having trouble with "hello world" because they forgot to include iostream.

$ cat unsigned.cpp #include <iostream> void f(unsigned int x) { std::cout << "x = " << x << std::endl; } int main() { f(-1); } $ g++ -Wall -Wextra -Wconversion -Werror unsigned.cpp $./a.out x = 4294967295 No error, no warning.