Our great sponsors
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
This leads to what actually happened to the proposal: the last formal talk on the proposal in a subgroup is way back in Kona (2019-02, by LEWGI). Since the proposal is handed over to LEWG, the only thing done with it is a mailing list review in 2021-02... which revealed several small issues that the author quickly fixed in R13 or a few revisions after. Most time in the mailing list was occupied by a discussion of name (colony -> hive), and the actual design is found to be pretty mature... Back then, a LEWG telecon is scheduled around 2021-11 or 2021-12 to discuss the matter, and assumedly that proposal will be forward to LWG and eventually land in C++23 if that actually happened.
Note that there are a number of issues with this approach, most notably that it doesn't necessarily play well with external build systems and with hermetic/reproducible builds. Rust is currently struggling with some of these issues, see e.g. https://github.com/rust-lang/rust-roadmap-2017/issues/12 and https://rust-lang.github.io/rfcs/2136-build-systems.html
I can make much more sense of C++ code to ensure that two build systems produce the same effect than I can parse and learn two completely unconnected programming languages deeply enough to do the same. I can unit-test core routines. I can as easily extract core logic into shared (configuration) files etc. The benefit of a standard is not to discourage alternatives but rather to agree on definitive semantics and shared and common needs (that is: in this case needs for interfaces to the compiler/linker). The implementation and general availabilty is just one of the by-product. The ability to do introspection in common terms is maybe the most consequential other product, and this is critical for 'transpiling' to other build systems and writing automated adapters such as the one that bazel is recommend for cargo's dependency management.