This should be updated as well:

https://matplotlib.org/stable/devel/dependencies.html#c-compiler

I see config changes and docstring changes, but no code changes. Are there more commits coming or is this it?

From my point of view, that is all. This is primarily intended toallow new features by keeping up with the rest of the ecosystem, but I am far from an expert in modern C++ and what we could actually use. I expect@anntzer or@ianthomas23 will have a better idea of that.

At the very least, I do know that mplcairo uses C++17 and so if we're finally at the point where we can allow it, then we can start thinking about integrating/depending on that in the future. Also, C++14 will be useful for some of the overload handling code in#27011 (which is why it doesn't currently build.)

There is a test failure. A blitting test using tk. No clue if it is related to a change in compilers.

Restarted the failed job. tk + blitting + osx is a known flaky test.

I expect@anntzer or@ianthomas23 will have a better idea of that.

One tangible benefit is use ofstd::optional (or possiblystd::variant) when passingnp.ndarray | None via pybind11 to C++ so that we can explicitly check theNone-ness rather than relying on automatic conversion to anp.ndarray and inferringNone based on thendims orshape.