On Tue Aug 12 16:39:07 2025 +0000, Elizabeth Figura wrote:
Regarding this issue, could we get the best of both worlds by using a generated vtbl rather than a compiled one, but #including it rather than linking to it? I'm not interested in bikeshedding (if I do have an opinion, I also prefer generated code to macros—I think they're far easier to read and understand for a newcomer), but the idea occurred to me and may allay concerns.
The MR now generates code that is #included, but there still is a macro, which we are arguing about, which lists all the functions which are expected to be implemented, in a "class vtable", so you can't miss one when using it.
There might be other ways than a macro, but its purpose is however that it allows compilation errors over link errors and I think it's an important criteria not to be discarded.