profiling/memory: tiny fixups of a couple of copy/move aspects.

I've been playing around with getting clang-tidy to run on the codebase, caught
a couple of things in profiling/memory that look reasonable to apply. What do
you think?

Note that there was also a note on an explicit std::move of a
trivially-copyable type, but I decided to keep it as is (in case the enum
becomes non-trivial to copy):
  src/profiling/memory/socket_listener.cc:123:64: warning: std::move of the variable 'cfg' of the trivially-copyable type 'perfetto::profiling::ClientConfiguration' has no effect; remove std::move() [performance-move-const-arg]

Change-Id: Iffbeaeceaad575c5b78c852096a58b845d9a2f55
3 files changed
tree: 8716551f92ce0ec5d2dbd782f04336947d999314
  1. build_overrides/
  2. buildtools/
  3. debian/
  4. docs/
  5. gn/
  6. include/
  7. infra/
  8. protos/
  9. src/
  10. test/
  11. tools/
  12. ui/
  13. .clang-format
  14. .gitignore
  15. .gn
  16. .travis.yml
  17. Android.bp
  18. Android.bp.extras
  19. BUILD.gn
  20. codereview.settings
  21. heapprofd.rc
  22. MODULE_LICENSE_APACHE2
  23. NOTICE
  24. OWNERS
  25. perfetto.rc
  26. PRESUBMIT.py
  27. README.chromium
  28. README.md
README.md

Perfetto - Performance instrumentation and tracing

Perfetto is an open-source project for performance instrumentation and tracing of Linux/Android/Chrome platforms and user-space apps.

See www.perfetto.dev for docs.

Bugs

  • For bugs affecting Android or the tracing internals use the internal bug tracker (go/perfetto-bugs).
  • For bugs affecting Chrome use http://crbug.com, Component:Speed>Tracing label:Perfetto.