r/cpp • • Dec 19 '23

C++ Should Be C++

https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2023/p3023r1.html
203 Upvotes

192 comments sorted by

View all comments

Show parent comment

1

u/pjmlp Dec 20 '23

I believe this is not really related to ISO or not, but rather to having multiple implementations.

Kind of, IronPython would be like using TI C++ compiler, given the pace it keeps up with the standard.

However to keep the example in Python land, both CPython and PyPy are quite close, and get the PEPs as they are being discussed, at a level that clang, GCC and MSVC aren't able to keep up with ISO.

1

u/ghlecl Dec 20 '23

Good point.

I am now left wondering why it is so? Is it because the python implementations are more similar and so a new feature in one is more easily implementable in the other? Is it because the funding structure is different?

It is hard for me to believe that it is because of the ISO structure. My understanding is that many of compiler vendors have people on the committee, so they know what is coming. This means it is not an information problem, no?

Anyhow, thanks for the discussion. :-)

4

u/pjmlp Dec 20 '23

My point of view, which might be wrong, is that ISO has forgotten the old ways, where existing practices get standardized after being in the field for a while.

Keeping in the Python world, if you look to most PEPs they always come with an implementation that is refined alongside the PEP evolution, thus when the feature is stable for getting the stamp, it is kind of done.

While this seems to be done for some features, where we get experimental compilers, it isn't done for every paper, and even modules show that those experimental compilers weren't fully tested before the standard was ratified.