Herb Sutter

> Raw pointers are fundamentally problematic if we have to do pointer arithmetic or offset based access. A major source for pointers, that we inherited from C, are strings. I...

Thanks. I'm slowly overhauling the regressing testing to run the tests, and I plan to also do that in bach. I'll defer this until then, I won't get to it...

Interim ack: Thanks! Yes, I've been meaning to add chaining. I was thinking of implementing it later in the same function and remove this special case part of the function...

Right, at the moment UFCS is hardcoded for just `x.f(...)` at a single level. When I fix the other issues about chaining it should fix this too, but it may...

Thanks, let me know what you find!

Hi everyone, I appreciate all the feedback. In a nutshell, the reason for a distinct syntax is summarized in [this 1-min clip from the talk](https://youtube.com/clip/Ugkxv4rzNcsFk9-3yziYu1uqBt2SZIUR_uZL) and if you have more...

Editors call: This would invert the guidance and we agree with the current guidance -- self-move should be a no-op.

Editors call: We will update the example to say that this is an example of code that would break without the test.

Editors call: We should - change `return make_tuple(a,b);` to `return {a,b};` - mention that returning large objects may move (e.g., `return {std::move(a), std::move(b)};`). - in the `get_string` example, where we...

Editors call: We agree with code locality. We think ES.77 correctly says to minimize (but not avoid or eliminate) `break` and `continue`. Some other rules we have cover code locality...