3 ms·
In C/++ land the implicit buffering causes all kinds of confusion among beginners and veterans alike. From “why does this not print” to “why is the performance
by eska 5y ago
In C/++ land the implicit buffering causes all kinds of confusion among beginners and veterans alike. From “why does this not print” to “why is the performance so bad in multithreaded programs”. In practice people avoid C and C++ I/O and use platform-specific functions to have more control over the buffering. Good job!
There are also other reasons for designing it this way such as composability. In general it’s bad idea to try to undo an abstraction, and instead one should build on top of primitives instead.