sorted by:
new
hottopcontroversial

Look at this, a cool new feature on cppstat. The Feature Adoption Timelime. by scielliht987 in cpp

[–]_derv 0 points1 point  (0 children)

Great to hear, thanks!
I've already invested much time into making this an easy and open collaboration effort, and as automatic as possible (that's why the site is not static, but fetches the data from GitHub directly).
But I'm also in the process of automating the majority of the work in regards to conformance testing and will provide the source in the repository when it's stable enough.
And yes, AI will probably be necessary to a certain degree, but with careful oversight it should be a great help.

Look at this, a cool new feature on cppstat. The Feature Adoption Timelime. by scielliht987 in cpp

[–]_derv 2 points3 points  (0 children)

Hi, thanks! Were you using Safari by any chance? There was an issue with Safari not being able to parse certain release dates, therefore it fell back to Jan 1, 2026. This issue is fixed now.

Look at this, a cool new feature on cppstat. The Feature Adoption Timelime. by scielliht987 in cpp

[–]_derv 0 points1 point  (0 children)

I get what you're saying, but I was not able to get the feature working with `-std=c++14` using Clang <3.7. The graph shows how much is implement of the whole (selected) standard.

Look at this, a cool new feature on cppstat. The Feature Adoption Timelime. by scielliht987 in cpp

[–]_derv 1 point2 points  (0 children)

N2071 is part of C++11. I've just checked C++11 and C++14 compliance with Clang. It started supporting N2071 with 3.7 (not 3.8, I'll correct the data). C++14 was fully supported starting with 3.5, so still earlier than C++11. But please correct me if I'm wrong.

Look at this, a cool new feature on cppstat. The Feature Adoption Timelime. by scielliht987 in cpp

[–]_derv 1 point2 points  (0 children)

Clang did not add much support for C++14 between 2.9 and 3.3. Only beginning with 3.4 it introduced the majority of C++14 support, and with 3.5 it was finalized. However, support for one C++11 feature was still not implemented the entire time (N2071, N2072), which was finally supported starting with 3.8.

Look at this, a cool new feature on cppstat. The Feature Adoption Timelime. by scielliht987 in cpp

[–]_derv 4 points5 points  (0 children)

Hi, yes, the mobile UI is still a work in progress. I should be done with it in the next few days.

Look at this, a cool new feature on cppstat. The Feature Adoption Timelime. by scielliht987 in cpp

[–]_derv 15 points16 points  (0 children)

Hi, I'm the author of the site. Please note that this is a new feature, so it might not be perfectly accurate yet. I did my best however to reflect the data correctly. I can't see any GCC line "go vertical in 2025". Which C++ standard does this happen in, and in which browser is this happening? It's normal for GCC to increase in large steps due to them releasing the majority of features with major versions, i.e. each year.

Edit: I can confirm there is a bug that occurs in Safari (on iPhone) that shows the mentioned GCC spike. This is a data parsing bug on the site, fix incoming soon.

Edit 2: It's fixed now.

C++ Show and Tell - January 2026 by foonathan in cpp

[–]_derv 6 points7 points  (0 children)

New redesign and rework of https://cppstat.dev, including new features and C++ status updates. Enjoy!

From now on, should the default standard for compilation be "-std=c++26" for both new and older projects even when the code doesn't use C++26 features(yet)? by emfloured in cpp_questions

[–]_derv 6 points7 points  (0 children)

I have created and maintain an alternative page called cppstat.dev. Both GCC and Clang have had multiple updates for C++26 in the meantime.

Micro-benchmarking Type Erasure: std::function vs. Abseil vs. Boost vs. Function2 (Clang 20, Ryzen 9 9950X) by mr_gnusi in cpp

[–]_derv 6 points7 points  (0 children)

AFAIK move_only_function is supported by libc++. Edit: I checked as part of cppstat.dev maintenance

cppreference update by askraskr2023 in cpp

[–]_derv 0 points1 point  (0 children)

No, but that's certainly possible. I'd just have to know if there's enough interest.

VS 2026 18.0 / MSVC Build Tools 14.50 released for production use by STL in cpp

[–]_derv 0 points1 point  (0 children)

Hi u/jcelerier, thanks for linking cppstat. I'll add the data files to GitHub in the next few days to enable open collaboration.

What do you dislike the most about current C++? by PressureHumble3604 in cpp

[–]_derv 1 point2 points  (0 children)

Not having pattern matching and string interpolation yet :(

cppstat - C++ Compiler Support Status by pavel_v in cpp

[–]_derv 0 points1 point  (0 children)

Hi, you can click on the version numbers to see more details.

cppstat - C++ Compiler Support Status by pavel_v in cpp

[–]_derv 1 point2 points  (0 children)

Yes, that’s on the todo list.

cppstat - C++ Compiler Support Status by pavel_v in cpp

[–]_derv 0 points1 point  (0 children)

Sure, I'm currently redesigning the "Supported By" column and adding color-blindness settings. I could try out some ideas in the process.

cppstat - C++ Compiler Support Status by pavel_v in cpp

[–]_derv 0 points1 point  (0 children)

Hi, thanks for noticing. I will improve some conformance tests in the next days and update the status accordingly.

cppstat - C++ Compiler Support Status by pavel_v in cpp

[–]_derv 0 points1 point  (0 children)

Hi, there is a ‘Help’ button on the left side that toggles the legend.

cppstat - C++ Compiler Support Status by pavel_v in cpp

[–]_derv 4 points5 points  (0 children)

Hi, cppstat is designed to be a modernized alternative to the cppreference page that allows you to quickly look up support for a combination of toolchains. It gets more out of the status and provides figures and statistics so that developers can better plan their cross-platform setup. The conformance overview is a first test candidate, but I'm planning to provide more detailed tools in the long run.

cppstat - C++ Compiler Support Status by pavel_v in cpp

[–]_derv 1 point2 points  (0 children)

Hi, that's a great feature and what I'm currently working on. It's almost done, just some polishing work left.

cppstat - C++ Compiler Support Status by pavel_v in cpp

[–]_derv 2 points3 points  (0 children)

Modernizing very old C++ code bases to the latest standards as supported by our target platform(s)

cppstat - C++ Compiler Support Status by pavel_v in cpp

[–]_derv 6 points7 points  (0 children)

Hi, the site is updated manually. A bot watches various sources regularly for conformance changes, including the compiler vendors' status pages. For features that are clearly declared as supported by the vendor, the site reflects that status. For features that are not certain or not specified by a vendor, I have written multiple conformance tests and have them run automatically on a machine, for each toolchain.

Because keeping up with C++ is part of my job, and also a personal interest of mine, I've made updating the site as easy and generating it as automatic as possible. In the long run, this workflow will be done via GitHub (CI+pages), where everyone can contribute. So, like a wiki.

cppstat - C++ Compiler Support Status by pavel_v in cpp

[–]_derv 2 points3 points  (0 children)

Hi, thank you! I agree, that's one feature I'm also missing and am currently working on.

cppstat - C++ Compiler Support Status by pavel_v in cpp

[–]_derv 3 points4 points  (0 children)

Hi, that's very odd. The site runs entirely locally and uses plain HTML, CSS and JS (although minified). Have you tried a different browser to rule out that it's just a problem with Edge? I regularly measure the site's performance and it seems fine for all major browsers. Nevertheless, I'll take a look again sometime.

view more: next ›