I've found adherence to C++ conventions in low-level software to be a rather contentious issue, mostly recently when working in an ML compiler group. One set abhorred the use of macros, the other any kind of polymorphism or modern C++ feature.

Coming from a background of working with OS kernels and systems software, I don't mind the kind of explicit "C++ lite" style used by the OP. Left to my own devices, I usually write things that way. I would think twice if I was trying to design a large framework, but ... I try to avoid those.

▲

einpoklum 3 days ago | parent [-]

If you think that, I encourage you to check out this presentation:

https://www.youtube.com/watch?v=zBkNBP00wJE

About writing a Commodore C64 game in modern(ish) C++

maybe it will sway you a bit :-)

	▲	caned 2 days ago \| parent [-]
		That is impressive. It certainly shows what is possible _if_ you are familiar enough with the intricacies of modern C++. I'm not sure how I feel about a workflow where one needs to continually address "overhead" introduced by the language environment.