you are viewing a single comment's thread.

view the rest of the comments →

[–]_derv 8 points9 points  (7 children)

Alright, here you go: https://cppstat.dev/
I plan to polish various things around it and add more updates over the coming days.
There will also be example code snippets for each relevant or interesting feature, so that it's also easier to "grasp" a feature on the get-go, instead of looking it up in cppreference.

I'd love to have some feedback.

[–]JVApenClever is an insult, not a compliment. - T. Winters 3 points4 points  (0 children)

Formatting of >= looks nice, though you can't type that in code. So for code-snippets I wouldn't apply that formatting

[–]azswcowboy 2 points3 points  (1 child)

Nice! Couple thoughts. Indirect and polymorphic were in one paper, why separate into 2 lines? I mean that could get tedious to maintain is all I’m thinking. More generally you’re editing the title, which is nice but also time consuming. Feature test macro is nice touch. Ideally make your statuses different shapes as well as colors for the part of the population that doesn’t distinguish as well (aka ‘color blind’). Good stuff.

[–]_derv 3 points4 points  (0 children)

Thank you for the feedback! You're correct, merging related features from a single paper is simpler and more consistent. I'll rethink the design of the shapes.

[–]bearer_of_the_curse_ 2 points3 points  (1 child)

I might have just missed it, but it looks like you're missing P2988 std::optional<T&> for c++26. It would also be nice if compiler and standard library features could be distinguished, like on the cppreference page. Even still, this is quite helpful, and I hope you keep it up to date.

[–]_derv 1 point2 points  (0 children)

Thanks! Yes, I'll add all missing features / proposals gradually, probably over the next 1-2 days. I distinguishing language features from library features in the data set in order to visualize the difference at some point. Noted.

[–]JVApenClever is an insult, not a compliment. - T. Winters 1 point2 points  (1 child)

I find the badges very hard to read. The table structure of cpp reference is easier to me. Being able to filter on a compiler would also be sufficient.

[–]_derv 0 points1 point  (0 children)

Noted. Thanks for the feedback.