C++26 is done: ISO C++ standards meeting Trip Report
herbsutter.com
C++26 is done: ISO C++ standards meeting Trip Report
1–10 of 437 posts
Re: C++26 is done: ISO C++ standards meeting Trip Report
#2Biggest open question is whether the small changes to the module system in this standard will actually lead to more widespread adoption
Re: C++26 is done: ISO C++ standards meeting Trip Report
#3This is awesome. I've was a dev on the C++ team at MS in the 90s and was sure that RTTI was the closest the language would ever get to having a true reflection system.
Re: C++26 is done: ISO C++ standards meeting Trip Report
#4I look forwards to getting to make use of this in 2040!
Proper reflection is exciting.
Re: C++26 is done: ISO C++ standards meeting Trip Report
#5Biggest open question is whether the small changes to the module system in this standard will actually lead to more widespread adoption
No. Modules are a failed idea. Really really hard for me to see them becoming mainstream at this point.
Re: C++26 is done: ISO C++ standards meeting Trip Report
#6Finally, reflection has arrived, five years after I last touched a line in c++. I wonder how long would it take the committee, if ever, to introduce destructing move.
Re: C++26 is done: ISO C++ standards meeting Trip Report
#7Biggest open question is whether the small changes to the module system in this standard will actually lead to more widespread adoption
The best thing the C++ WG could do is to spend an entire release cycle working on modules and packaging.
It's nice to have new features, but what is really killing C++ is Cargo. I don't think a new generation of developers are going to be inspired to learn a language where you can't simply `cargo add` whatever you need and instead have to go through hell to use a dependency.
Re: C++26 is done: ISO C++ standards meeting Trip Report
#8Great. C++20 has been my favorite and I was wasn't sure what the standards says since it's been a while. I'll be reading the C++26 standard soon
Re: C++26 is done: ISO C++ standards meeting Trip Report
#9Biggest open question is whether the small changes to the module system in this standard will actually lead to more widespread adoption
No, because most major compilers don't support header units, much less standard library header units from C++26.
What'll spur adoption is cmake adopting Clang's two-step compilation model that increases performance.
At that point every project will migrate overnight for the huge build time impact since it'll avoid redundant preprocessing. Right now, the loss of parallelism ruins adoption too much.
Re: C++26 is done: ISO C++ standards meeting Trip Report
#10Biggest open question is whether the small changes to the module system in this standard will actually lead to more widespread adoption
No. Modules are a failed idea. Really really hard for me to see them becoming mainstream at this point.
The idea is great, the execution is terrible. In JS, modules were instantly popular because they were easy to use, added a lot of benefit, and support in browsers and the ecoysystem was fairly good after a couple of years. In C++, support is still bad, 6 years after they were introduced.