On Windows I bumped the version to C++17 so I could use the C++/WinRT headers while prototyping translucent backdrops. No problems besides having to replace a few std::auto_ptr instances with std::unique_ptr. And having access to those headers made for much, much more readable code.
I also recommend C++20 instead of C++23. On Ubuntu 22 and 24 when I set the C++ standard to 23 the __cplusplus macro reports a version of 2021 (whatever that means). I had to get all the way up to Ubuntu 26 and gcc 15 for it to report full support for c++23. Personally I don’t need those sort of mysteries in my life. Martin > On Sep 21, 2026, at 9:17 AM, Kevin Rushforth <[email protected]> > wrote: > > I'd recommend no higher than C++20. I'm not sure all of our current > toolchains fully support C++23 on all platforms. By using C++20, we would > avoid the risk of hitting odd issues. > > Let's see what others think. > > -- Kevin > > > On 9/21/2026 8:44 AM, Nir Lisker wrote: >> I think that if we can update, then it should be to the most recent version >> we can afford, which is 20 or possibly 23. >> >> On Mon, Sep 21, 2026 at 6:27 PM Kevin Rushforth <[email protected]> >> wrote: >> >> WebKit uses C++23 (C++20 with some C++23 features used), so it seems >> reasonable to update the rest to a more recent minimum, perhaps >> C++17 or >> C++20. All of our current toolchains should fully support C++20. >> >> What do others think? >> >> -- Kevin >> >> >> On 9/21/2026 6:06 AM, Nir Lisker wrote: >> > Hi, >> > >> > The C++ version used for native compilation is 14, at least from >> what I >> > could see using MSVC on Windows. Is it possible to update it to >> > something more recent? >> > >> > - Nir >>
