C++20, How Hard Could It Be
docs.google.com
C++20, How Hard Could It Be
1–10 of 444 posts
Re: C++20, How Hard Could It Be
#2Writing Chromium grade C++ seems like a hard job with all these extrinsic rules and regulations to make it work
Re: C++20, How Hard Could It Be
#3Is there a case for or against incrementally adopting Rust ?
Re: C++20, How Hard Could It Be
#4As expected modules are relegated to some later time ("will be its own experiment")
Re: C++20, How Hard Could It Be
#5It's easier to say goodbye C++!
Re: C++20, How Hard Could It Be
#6Is there a case for or against incrementally adopting Rust ?
They are experimenting https://chromium.googlesource.com/chromium/src/+/refs/heads/...
Re: C++20, How Hard Could It Be
#7I stopped using C++ after lambdas were introduced (10 years ago or so?)
Is there anything I can read to get up to date quickly?
Re: C++20, How Hard Could It Be
#8Is one release really causing so many problems? I thought C++ treated backwards compatibility as a holy thing.
Re: C++20, How Hard Could It Be
#9Damn. May as well have used a language that isn’t released yet like Zig. That’s a ton of problems.
Re: C++20, How Hard Could It Be
#10Is one release really causing so many problems? I thought C++ treated backwards compatibility as a holy thing.
It doesn't cause problems as in old things don't work as in it takes time to get advantage of newly introduced ones and replace anything considered deprecated (edit: and rename variables clashing with new keywords).