Herb Sutter

Editors call: Thanks, we've reviewed this and we think we see where you're coming from. We believe that the guidance does actually provide a deterministic decision tree for how to...

Editors call: Thank you for bringing up the issue. We don't believe in qualifying everything to ease comprehension, but this does bring up the bigger issue of when and how...

Editors call: Are you suggesting that we require `narrow` or `narrow_cast` for all float->unsigned conversions, and that `narrow` gives "the right" value (as if it was an integer value) and...

I haven't looked at your code, but note that the Lifetime spec currently has a placeholder for shared ownership (e.g., shared_ptr) and owner-of-nonowner (e.g., vector) which are still to be...

That's it (not yet 1.0 because of fleshing out shared and owner-of-nonowner), and the section III is forthcoming with detailed rules tables of interest primarily to compiler writers and academics....

Sooner rather than later, but no firm ETA. Right now most of us who are taking the lead in the Guidelines are consumed with at a spike of standards work...

Editors call: The Guidelines currently target C++17, and coroutines are in C++20 which is not yet published. The Guidelines document consensus experience and guidance, so once C++20 is used in...

Editors call: Now that we're open for business for coroutines, we're reopening this... could you please submit a PR for a new guideline as you describe, with succinct rationale and...

Editors call: We are reopening this because it's needed. We do want to rely on the standard for specification (which we can now do with `span`, the only difference in...

Editors call: @gdr-at-ms and @ChrisGuzak have converged on a solution and @gdr-at-ms is assigned to implement it.