Herb Sutter
Herb Sutter
Clarify C.67 and C.130 to say that suppressing copy construction should mean not having a public one, and that the Clone pattern could be done in terms of a private...
The last line prints `1`, but it should print `2` because `f(param)` is the definite last use of the `param`... Godbolt repro: https://cppx.godbolt.org/z/17noYP ``` struct X {}; void f(X const&)...
The basic case is: void move_in(move auto a, in auto b) { copy_from(a, b); } // ... move_in(std::move(s), s); This bug seems fragile... each of the following repros sometimes crashes...
When an `in` parameter is copied (type is small and trivially copyable), there's no need to pass an extra bit to remember whether it was a non-const rvalue. Repro 1,...
`forward` parameters are not yet implemented. Repro: https://cppx.godbolt.org/z/WrarG3
Variadic parameters don't yet work. Example: `void f(in int ...ts)`. Repro: https://cppx.godbolt.org/z/3bGrxM
F.16 says: > (Simple) ((Foundation)) Warn when a parameter being passed by value has a size greater than 2 * sizeof(void*). Suggest using a reference to const instead. > (Simple)...
We have; - [C.60: Make copy assignment non-`virtual`, take the parameter by `const&`, and **return by non-`const&`**](https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#Rc-copy-assignment) - [C.63: Make move assignment non-`virtual`, take the parameter by `&&`, and **return...
Now that the initial documentation is complete, I can spend more time writing and reviewing code, and catching up with issues and PRs. What would help me is: **If there...
If so, should we change their names per Sean Parent's comment at https://github.com/microsoft/GSL/issues/1032 ?