I don't think there's a timeline for C++23 in V8 yet. For the time being, V8 is still on C++20.
I wouldn't expect that the schedule necessarily matches previous C++ version rollouts. New C++ versions are relatively infrequent and each is different, so it's a case-by-case decision, driven by factors such as: - Does the new C++ version offer anything that we'd want to use? - Does switching require any extra work, and when can we prioritize that work? - Are there any blocking concerns from embedders? We are well aware of the balancing act. Right now for C++23, I think we want to give embedders a bit more time, but I don't know how much time that might be. Is there a particular reason for your question? On Fri, Apr 10, 2026 at 9:16 AM 'James Dennett' via v8-dev < [email protected]> wrote: > Now that Chromium allows (some) use of C++23 features, is there a > plan/policy/path to doing the same in V8? Is this documented anywhere? > (My Google-fu has failed me, if so.) > > Given that this is something of a balancing act between the benefit to V8 > developers and the needs of V8 integrators ("users"), is this decision made > in approximately the same way for each C++ update? Would it be a > reasonable approximation to guess that V8 might break C++20 compatibility > around three years after requiring it (and breaking C++17 compatibility), > which would put this around June 2027, or is there a realistic chance that > it might happen much faster for C++23 than for C++20? > > -- James > > -- -- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev --- You received this message because you are subscribed to the Google Groups "v8-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/v8-dev/CAKSzg3SNky3PcJYqUkpTF%2BZ%3D4zhS7WYPGzpHnU7zOTHJzrTQhA%40mail.gmail.com.
