Hi Phil,

so you want metaprogramming facilities to autogenerate code.

The current direction is to first get static Reflection integrated into the standard and build metaprogramming facilities from there. This is a huge topic and is planned to be finished 2029+++

Do you know those papers:

P1240R2: Scalable reflection in C++

https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2022/p1240r2.pdf

P2320R0: The Syntax of Static Reflection

https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2021/p2320r0.pdf

P2237R0: Metaprogramming

https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2020/p2237r0.pdf

 

If you have specific feedback for the current direction of reflection or involve yourself to help resolve all the issues and bring e.g. Static Reflection to C++26 and Metaprogramming to C++32, you should read deeper those and related papers and then write to the authors.

 

C++ will get a thought-out general solution for metaprogramming, not a quick-fix. This will take some time.

 

In the meantime, there are smartpointers in the standard library and external libraries, and code preprocessors and memory checkers, which bind themselves to a program or within the Standard Libraries.

 

Best,

Sebastian

PS

There was a talk on Cppcon by Andrei Alexandrescu: Reflection in C++, where he talks about current and future generic programming.

https://cppcon.digital-medium.co.uk/session/2022/reflection-in-c/

It currently probably is not available free of charge yet, but for an online conference pass.
 

-----Ursprüngliche Nachricht-----
Von: Phil Bouchard <boost@fornux.com>
Gesendet: Di 27.09.2022 18:21
Betreff: Re: [std-proposals] Rust vs C/C++ vs C++ Superset
An: std-proposals@lists.isocpp.org;

What I would like to integrate into the C++ standards first and foremost is a framework to allow implicit addition of class members, parameters, and scope instances, just like what the C++ Superset source-to-source compiler is doing right now.