Passing a symbol to std::move that is marked const is a no-op, which can be fixed in two ways:
- Remove the
const, or - Remove the
std::move
Passing a symbol to std::move that is marked const is a no-op, which can be fixed in two ways:
const, orstd::move<!--e57a25ab6845829454e8d69fc972939a-->
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
<!--174a7506f384e20aa4161008e828411d-->
Reviewers, this pull request conflicts with the following ones:
If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first.
4 | @@ -5,6 +5,7 @@ misc-unused-using-decls, 5 | modernize-use-default-member-init, 6 | modernize-use-nullptr, 7 | performance-for-range-copy, 8 | +performance-move-const-arg,
Good idea to add this.
Locally, on aarch64, I see that the BlockToJsonVerbose benchmark is about 2% faster.
Also, for some unknown reason, the BlockToJsonVerboseWrite bench uses 5% less memory?
Code review ACK fa875349e22f2f0f9c2c98ee991372d08ff90318. Looks good. Good for univalue to support c++11 move optimizations