3 ms·
It's a testament to the hard work of the language designers and committee members that they're able to grow the language at such a rapid pace. It's exciting to
by logicchains 6y ago
It's a testament to the hard work of the language designers and committee members that they're able to grow the language at such a rapid pace. It's exciting to think that the C++ I write in 5 years' time will probably be completely different from how I'm writing it now, due to things like meta classes, ranges, modules, concepts and reflection. Few other languages are adapting so quickly.
- dgellow 6y agoMeta classes in 5 years? You're optimistic :) For those who don't know, there is a short video from fluentcpp: https://www.youtube.com/watch?v=v9eJE2m3CYk https://www.youtube.com/watch?v=v9eJE2m3CYk (and a transcript if you prefer: https://www.fluentcpp.com/2018/03/09/c-metaclasses-proposal-less-5-minutes/ https://www.fluentcpp.com/2018/03/09/c-metaclasses-proposal-...). And the proposal from Herb Sutter is here: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2018/p0707r3.pdf http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2018/p070...
- pjmlp 6y agoThey better do it, after all that is the reasoning behind the Microsoft internal politics to kill C++/CX via C++/WinRT. That now we have an ISO C++17 compliant framework and are supposed to wait for ISO C++23 reflection until Visual C++ team bothers to provide the same level of UWP/XAML tooling that C++/CX enjoys since 2012. Until then, C++/WinRT provides a revivalist experience for those that missed the opportunity to deal with bare bones IDL file editing alongside ATL.
- RandoHolmes 6y agoI think what's a testament is that everything you say is true and they'll do it while maintaining backwards compatibility with code written 35 years ago.