This often gets over-reported; old memes die hard. There's a small number of macros that a custom preprocessor expands to (very pedestrian) generated code, but

This often gets over-reported; old memes die hard. There's a small number of macros that a custom preprocessor expands to (very pedestrian) generated code, but they are optional to use (though it's certainly uncommon not to use them) and these days there's template-based versions of some of them that are preferred and steadily finding adoption over the macro ones because they're superior. Beyond that there's a few more normal preprocessor-based macros that are entirely optional. In that sense Qt also tracks vanilla C++ very closely and has adopted features from newer language versions at a fairly steady pace and swiftly for such a large production library set. None of this matters much to my point though - that was about much more basic language semantics like classes-based OOP and the absence of ownership rules.