On Tue Aug 12 15:26:44 2025 +0000, Rémi Bernon wrote:
I think it should, in this particular case, because it's all about developer QoL and compilation errors play very nicely with LSP tools, while link errors do not and are a pain to deal with, and IMO even worse than the current situation, as verbose as it is to write. I'm happy to make adjustments and to improve the experience for different use cases than mine but I'm ofc primarily interested in making my life easier in the first place, and won't be interested in making it worse.
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.