4 ms·
C++ should probably look at the Epochs rust is using to manage compat issues so old code still compiles but they aren't completely bound to old things (see how
by runevault 4y ago
C++ should probably look at the Epochs rust is using to manage compat issues so old code still compiles but they aren't completely bound to old things (see how they added keywords for async in 2018 as an example).
- tialaramex 4y agoThe Rust feature you're thinking of is named Editions. The proposal (from Vittorio) to do this in C++ 20 was named Epochs, and the committee rejected it, taking the position that while this is maybe a good idea they're not interested in figuring out how to do it and will meanwhile make it harder. It would definitely be very difficult to do Epochs in C++ 20. It got harder, and will continue to get harder. In my view, if it was possible in 2020, it won't be possible in 2026. Accordingly I think C++ is doomed. Get out while you still can (or, you know, size up lucrative consulting gigs as maintenance, it's not as though existing C++ code will all rust out [pun not intended] before you retire)
- steveklabnik 4y agoSomeone did write up a paper for this, but it isn’t happening; I can’t remember if it was rejected formally or what exactly happened, all I remember is it’s not happening.
- runevault 4y agoThat is unfortunate to hear, but I've already started learning rust and not doing c++ for the day job so I guess it doesn't impact me terribly.
- steveklabnik 4y agoHere's the paper, if anyone is curious: https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2019/p1881r0.html https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2019/p18...