Sergey Zubkov

Yes, I am on the hook to do all of #811 but feel free to put a PR in for this one.

That's @hsutter 's "M&M rule" (mutable and mutex go together): https://herbsutter.com/2013/05/24/gotw-6a-const-correctness-part-1-3/

gave it a shot colorizing P.1 in gh-pages it colorizes when viewed on github https://github.com/isocpp/CppCoreGuidelines/blob/gh-pages/CppCoreGuidelines.md#Rp-direct but not on gh-pages, generated HTML confusingly says `` http://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#Rp-direct I wonder if we're missing...

there we go, http://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#Rp-direct now shows how it looks with CSS produced by `rougify style github` Still, the colors on github's own viewer look much better (they appear to come...

To be fair, as-is http://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines.html has that "Turn ON Syntax" button that colors it up. But backticks-cpp may still be a good idea

Thanks to #1756 there is now a coroutine rule section, feel free to add!

if you `#include `, you can use `std::size_t`, if you `#include `, you can use `size_t` As for which headers to include for C library types (`stddef.h` vs `cstddef`, `stdint.h`...

same as #811 which I should really find time for

I.10 makes a distinction between failing and returning a status (..."to report what are really status codes, rather than errors."). Non-ignorable status codes are pretty cool though, and could have...

I'd say C++20 ranges include this functionality as [views::take_while](https://en.cppreference.com/w/cpp/ranges/take_while_view). For example, ``` int a[] = {1,2,3,0,-1,-2,-3}; auto up_to_zero = views::take_while(a, [](int n){return n != 0;}); for (int n: up_to_zero) std::cout...