3 ms·
"using namespace std;" goes a long way to make C++ more readable and I don't really care about the potential issues. But yeah, due to a lack of a nice module sy
by m-schuetz 10mo ago
"using namespace std;" goes a long way to make C++ more readable and I don't really care about the potential issues. But yeah, due to a lack of a nice module system, this will quickly cause problems with headers that unload everything into the global namespace, like the windows API.
I wish we had something like Javascript's "import {vector, string, unordered_map} from std;". One separate using statement per item is a bit cumbersome.
- delta_p_delta_x 10mo agoStandard library modules: https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2022/p2465r3.pdf https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2022/p24... I have thoroughly forgotten which header std::ranges::iota comes from. I don't care either.
- m-schuetz 10mo agoLast time I tried, modules were a spuriously supported mess. I'll give them another try once they have ironclad support in cmake, gcc, clang and Visual Studio.