3 ms·
> This presentation seems to show the compatibility between most recent releases is not very good. Half of the "features" shown in the presentation are exceedi
by MauranKilom 4y ago
> This presentation seems to show the compatibility between most recent releases is not very good.
Half of the "features" shown in the presentation are exceedingly niche. It's just that a 20 million LOC (or however many Chrome has right now) code base is almost guaranteed to exercise every niche feature somewhere.
Having helped with C++ standard transitions of a code base half an order of magnitude smaller, the amount of issues requiring code changes was minuscule so far. You tend to have much more boring problems, like:
- "We can't use newer C++ because C++/CLI doesn't support it"
- "We can't use newer C++ in these headers because they end up included in CUDA code, and that compiler only supports C++14"
- "We have to wait for a new version of <tool> before we can lint/sanitize/profile/format our code"
- "This third-party code has the compiler up in arms now because it does questionable things"
- pjmlp 4y agoYep, C++/CLI is stuck on C++17, and apparently will stay like that.