Herb Sutter

Editors call: F.18 covers that for "sink" functions (for smart pointers, ownership transfer) to pass by `&&`. In our desire to keep the smart pointer passing rules simple and avoid...

Editors call: We think the Enforcement gives a clear size, but agree with @cubbimew that the Enforcements (and probably the Guideline) should additionally be triggered only when the type is...

Editors call: We agree that every absolute size is unlikely to be always correct. But we don't think that passing by reference is always acceptable (e.g., sometimes it creates a...

Agreed, thanks.

OK, reopened to discuss with editors. Note that by "base class" we mean a class designed to be used as a base class where calling code passes by pointer/reference and...

Editors call: Even though it's a C++20 features and the Guidelines don't yet support/require C++20, enough people are interested in this that we should say something. Assigning to @GabrielDosReis. Thanks!

Editors call: Thanks! We like the approach of qualifying the first one with `ranges::` and removing the second one that uses `par`. Also update the reference to the Ranges TS...

Editors call: We will look to see if we can make this clearer.

Editors call: We think C++26 ought to treat `return local;` as a non-const rvalue (not just an rvalue). In the meantime, we should add a Note or Exception to this...

Editors call: We think the current rule is reasonable, but we're open to extending the Enforcement to be more flexible/tasteful than allowing only `0`, `1`, and `nullptr`. Any suggestions?