Re: State and plans for C++20 module support?

On 2/18/25 13:32, Zack Weinberg wrote:
> Autoconf includes logic to probe for various compiler features and
>     for adequate support for various levels of the C and C++ standards.
>     These probes have a bunch of problems and they currently don't
>     include anything newer than about 2017 for either C or C++.

Actually, I contributed support for C23 to bleeding-edge Autoconf. But 
as I avoid C++ there's nothing in Autoconf yet for C++20 or C++23.


>     the biggest problem with them is NOT that they
>     are out of date, but that they do not allow the package being
>     configured to declare which edition of the language standard they
>     want.

For C this has not been a major problem as far as I know. There should 
be simple workarounds for bleeding-edge Autoconf as-is, though of course 
it would be nice to make Autoconf better.

C++ is a different beast, though. It'd be helpful to get real C++ 
expertise involved here.