Sergey Zubkov

At least in my team the accepted style is to prefer (tag-dispatched) overloading where possible, specifically to "keep functions short and simple" - we've seen an innocuous `if constexpr` or...

I think the options for self-moving classes with STL members are * let them do what their authors believe is right (then "self-move no-op" only applies to pointers etc) *...

For every reasonable expectation of operator overloading, there is [boost.spirit](https://github.com/boostorg/spirit/blob/develop/include/boost/spirit/home/qi/string/symbols.hpp#L321)

there are [two exceptions](https://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md#exceptions-2) noted in Con.1, at least it should be linked from ES.25

there was some discussion of the use of `const` with function parameters in https://github.com/isocpp/CppCoreGuidelines/issues/1081

> we need ifdefs around suppressions to make sure they even compile. Sounds like a compiler bug: [dcl.attr]p6 says [Any attribute-token that is not recognized by the implementation is ignored](http://eel.is/c++draft/dcl.attr#grammar-6.sentence-2)

Chaining might be red herring as it's just a special case of lvalue use. Though I agree I can't recall intentionally using assignment expressions that way outside of old C's...

I'd say "member variable" relates to "non-static data member" like "method" relates to "non-static member function". One is a general programming concept, the other is how C++ makes it happen....

would be neat to also show "Bad" example, except what is the implied alternative? Even old C++ `std::char_traits` and `Loki::TypeTraits::UnConst` were templates..

Guidelines describe what GSL should provide, implementations do their best to make it happen. If there's interest in finalizing Microsoft's implementation of gsl::joining_thread, perhaps restarting https://github.com/microsoft/GSL/pull/582 would help, but it's...