papers

What's fun is, because everything is decided in papers, we can find out why! https://github.com/cplusplus/papers/issues/884 Accepted paper here: https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2022/p20... > The proposed std::print function improves usability, avoids allocating a temporary std::string object and calling operator<< which performs formatted I/O on text that is already formatted. The number of function calls is reduced to one which, together with std::vformat-like type erasure, results in much smaller binary code (see § 13 Binary code). Additionally, > Another problem is formatting of Unicode text: > std::cout << "Привет, κόσμος!"; > If the source and execution encoding is UTF-8 this will produce the expected output on most GNU/Linux and macOS systems. Unfortunately on Windows it is almost guaranteed to produce mojibake

Bringing editions to C++ failed, and I am not aware of anyone trying to tackle the issues https://github.com/cplusplus/papers/issues/631 (I could be wrong though! I follow the committee more than you may guess, but not as much as to think I know everything about what's going on.)

There was an attempt to bring this to C++ but it ran into some roadblocks https://github.com/cplusplus/papers/issues/631

Never say never, there is P2656. We'll see! It's more about making things interoperable than mandating a new tool, but it's still something useful in this space. It also links to previous work. https://github.com/cplusplus/papers/issues/1323

GitHub would not be relevant in this respect because: * It's owned by a (single) commercial corporation, Microsoft. * There is censorship both by content and in some respects by country of origin. * The code is closed. but otherwise it's an interesting idea. The C++ standardization committee uses GitHub to track papers submitted to them, see: https://github.com/cplusplus/papers

You subscribe to the Github issue of the proposal: https://github.com/cplusplus/papers/issues

This was not the reasons cited in the actual votes to postpone https://github.com/cplusplus/papers/issues/631#issuecomment-... Not that that means you're strictly wrong, mind you, just that only textual inclusion issues and template issues were voted on as being blocking at that time.

Just as a tiny FYI, Rust's editions were proposed for C++ in 2019: https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2019/p18... The outcome: https://github.com/cplusplus/papers/issues/631#issuecomment-...