3 ms·
Doesn't seem extremely limited at all: - Exceptions, RTTI, thread_local, Statically constructed object all require runtime support and are problematic in a ker
by gpderetta 6y ago
Doesn't seem extremely limited at all:
- Exceptions, RTTI, thread_local, Statically constructed object all require runtime support and are problematic in a kernel so it is not surprising
- Virtual inheritance: almost litterally nobody uses it.
- initializer lists require static storage which is also problematic in a kernel
- operator overloading and trailing return types are a stylistic choice, but at the end of the day they are a tiny bit of C++
Things that are allowed: actual OO classes inheritance (including multiple inheritance), virtual functions, RAII, templates (no restrictions at all), lambdas, all the recent goodies. I.e. all the things that make C++, well, C++.
So it is way less restricted than other guidelines I have seen for well known C++ projects.