
It is possible to write standard C++ with memory safety guarantees similar to Rust by the end of
17
1kṀ27402038
1H
6H
1D
1W
1M
ALL
8%
2027
25%
2030
33%
2033
51%
2037
Requires specification in a standard (presumably CPP26/29/32, but a change in cadence or fork/alternative that is a formal standard would be acceptable) and usable by programmers in at least one open source implementation (eg gcc or clang, but something new/newly open source would qualify).
Question inspired by https://safecpp.org/ but it does not need to be this proposal or a derivative that is accepted and implemented to resolve to true.
Added: If 2027 is judged yes, so will 2030, 2033, and 2037. If 2030, also 2033 and 2037. If 2033, also 2037. I will trade.
This question is managed and resolved by Manifold.
Get
1,000 to start trading!