Herb Sutter

Editors call: Thanks! This looks good, just waiting to see if there's a last reply from @apenn-msft and then this is ready to merge.

Editors call: We agree that placement `new` isn't really "new", it's C++'s idiomatic quirky way of spelling "invoke the constructor." So we should add an exception to this item since...

The exception should however still say that it's for low-level manual lifetime management and should have a corresponding `destroy_at` or explicit destructor call, and typically should be hidden away inside...

Editors call: We'll update the Guidelines as a whole for C++20 in the future, but we agree these parts can be updated now... @cubbimew will update these existing parts now...

Editors call: We want the rules to be general because they are aimed at programmers, and the Enforcements to be specific because they are aimed at tool implementers. Perhaps we...

Editors call: We tend to agree. The original motivation is more when `continue` are sprinkled throughout the loop body and especially when they are nested. The actual example here is...

Editors call: This is a real problem but not one the guidelines deal with today. The guidelines mostly focus on using C++ well in valid programs. We usually don't have...

Editors call: The default answer is that it should work with custom arithmetic types, if there is no difference in performance. If making it work with custom arithmetic types has...

Editors call: Is this basically the same issue as the one about banning reference parameters, and perhaps the two could be handled together/merged?

We have this in [C.12](https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#Rc-constref) so perhaps a PR to propose updates to that?