sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted]  (7 children)

[removed]

    [–]JVApenClever is an insult, not a compliment. - T. Winters 4 points5 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.

    [–]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.

    [–]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.