Sergey Zubkov

could even make it complete with `(std::cout

the intra-document links are intended to be useful here: https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#S-interfaces #2198 fixes the links in github document, though we need to finish reviewing it

There's [F.25: Use a zstring or a not_null to designate a C-style string](https://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md#f25-use-a-zstring-or-a-not_nullzstring-to-designate-a-c-style-string) which can be seen in action in many examples in the guldelines, such as [F.22: Use T*...

> And Wide characters are required when writing in languages like Chinese where all of their letters (or symbols) are wider than english letters. not really, if you're on an...

> Please stop mixing up unicode and UTF-8. I did not use a `u8 ` string literal on purpose. That example would work as expected on any system that supports...

I believe this is a dup of https://github.com/isocpp/CppCoreGuidelines/issues/1263 which was resolved back then against adding copy-swap assignment to C.21 That said, cppreference discusses the issues with copy/swap assignment, both in...

If I were to see `void run_task(const std::shared_ptr &arg)` in code review, I'd say "please change to `void run_task(const Task& arg)`. > Here run_task cannot know it has been provided...

> For example, aliasing violations or signed integer overflow. apropos the infamous felix-gcc bug report https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30475

Ref-qualifiers were previously rejected in https://github.com/isocpp/CppCoreGuidelines/issues/1296

> I suggest a rule [SF.?23?] that every .h file in the project is included as the first file in at least 1 (one) .cpp file. As-is, that would flag...