3 ms·
I don't normally get into C/C++ or kernel chats, but I hope they choose something different than C++, maybe Zig. The problem with C++ is that like Scala, it's h
by karmakaze 3y ago
I don't normally get into C/C++ or kernel chats, but I hope they choose something different than C++, maybe Zig. The problem with C++ is that like Scala, it's hard to stick to a subset without realizing you've used more than intended after the fact. Maybe the kernel team could do it since there's a culture of keeping things clean/simple.
- kreetx 3y agoI think they'll likely agree on some C++ subset when getting into it so I wouldn't be worried. Though, why not just evolve C itself with those features? C is evolving, too, and this could be used as a vehicle for it.
- teleforce 3y agoPerhaps they should just jump straight to D. The proposed C++ 20 is like D-- given how many D features have been adopted over the years. Now that D supports C native compilation and supported by GCC eco-system so the conversion can be done in peacemeal, it will be win-win situation for safety, convenience, power and flexibility. One of the main reasons of switching to C++ given is for templates, and D templating system is second to none. D also run and compile as fast as C, and the latter cannot be said to C++. For kernel developers fast compilation will be necessary not a luxury. Imagine kernel development in D without GC and user level development with D with the default GC, it really looks like a match made in heaven to me.