105K views · Sep 28, 2017 · 1:47:45 · 2 HN recommenders · 4 mentions · discussed 2017–2020
At CppCon 2017 Herb Sutter presents his work on evolving C++ through compile-time code generation, including metaclasses and reflection. The aim is to make the language both more powerful and simpler by letting programmers express intent directly.
Why Hacker News points people here: Praised as the best talk of CppCon 2017 and the key introduction to metaclasses and generative C++.
“Herb Sutter's talk about it is by far the best talk I've seen from from CppCon17.”HN comment, 2017
“Herb Sutter's talk about it is by far the best talk I've seen from from CppCon17.”
Sutter on generative C++ and metaclasses; best CppCon17 talk.
Herb Sutter's talk about it is by far the best talk I've seen from from CppCon17. "Meta: Thoughts on generative C++" - this video
“The talk about the reflection proposal was amazing. Meta classes are also very cool.”
Reflection proposal and meta classes in C++.
The talk about the reflection proposal was amazing. Meta classes are also very cool. We can only hope it comes fast. this video
“Herb Sutter proposed Python-like metaclasses in C++ through compile-time code generation.”
A few years ago Herb Sutter proposed Python-like metaclasses in C++ through compile-time code generation. Not sure if anything has been proposed for general use. this video
To a degree, but templates and constexpr don't support a bunch of features like compile-time field enumeration and introspection + code generation. For example, let's say I have a bunch of structs: struct GeoCoordinate { int lat, long; }; struct GeoArea { std::vector<GeoCoordinate> perimeter; }; struct Place { std::string name; std::string contact_number; GeoArea area; }; Now I need to serialize these structs into a format to be sent over the wire. Currently, I have a few choices: 1. Use an off-the-shelf library like protobuf (disclaimer: I work for Google). Then I have to convert my code to a protobuf definition and rely on its code generator to perform [de]serialization. I also have to hope that my library supports all the field definitions I need. 2. Write macros to define each field in each structure. These macros perform some arcane magicks that somehow create the necessary [de]serialization functions. These macros are difficult to write and maintain (or I find a library). 3. Manually define the methods myself. This is tedious, hard to maintain, and error prone. What if I could write some code in C++ which could read the structure and generate the appropriate serialization code? Something like (syntax hypothetical): Serializable(Class) { std::string serialize() { std::string output; for (auto member : Class.members()) { // loop unrolled at compile time if (member.type == int) { output.append(std::format("{:10}"), member.get()) } else if (member.type == std::string) { ...
