Add curly braces to control statements in modules/webaudio.

Not all of these are to fix coding style guide violations, but some are.  Regardless of the style guide, including the braces in all control statements will make it easier to identify branches and also easier to modify the code more safely in the future.

This change was performed automatically using clang-tidy with the following steps:

1) Add the following to custom_vars in .gclient:  'checkout_clang_tidy': True,

2) Run: gclient runhooks

3) Build chromium and change to the build output directory (path_to_chromium/src/out/Default for me)

4) Run the following: gn gen . --export-compile-commands

5) Run the following command from the modules/webaudio directory: path_to_chromium/src/third_party/llvm-build/Release+Asserts/bin/clang-tidy -p path_to_chromium/src/out/Default -checks="-*,readability-braces-around-statements" -fix *.cc *.h

6) Run: git cl format

Reference: https://chromium.googlesource.com/chromium/src/+/HEAD/docs/clang_tidy.md

This change should NOT cause any performance or behavior changes.

Change-Id: I9fd70a545704f883cfb0e204fe45e39bd1da17ee
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3369279
Reviewed-by: Hongchan Choi <hongchan@chromium.org>
Commit-Queue: Michael Wilson <mjwilson@chromium.org>
Cr-Commit-Position: refs/heads/main@{#957815}
56 files changed
tree: 92f3fc3b5304a4c180609aa0233d2b63bf6a2f7a
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. cloud_print/
  13. codelabs/
  14. components/
  15. content/
  16. courgette/
  17. crypto/
  18. dbus/
  19. device/
  20. docs/
  21. extensions/
  22. fuchsia/
  23. gin/
  24. google_apis/
  25. google_update/
  26. gpu/
  27. headless/
  28. infra/
  29. ios/
  30. ipc/
  31. jingle/
  32. media/
  33. mojo/
  34. native_client_sdk/
  35. net/
  36. pdf/
  37. ppapi/
  38. printing/
  39. remoting/
  40. rlz/
  41. sandbox/
  42. services/
  43. skia/
  44. sql/
  45. storage/
  46. styleguide/
  47. testing/
  48. third_party/
  49. tools/
  50. ui/
  51. url/
  52. weblayer/
  53. .clang-format
  54. .clang-tidy
  55. .eslintrc.js
  56. .git-blame-ignore-revs
  57. .gitattributes
  58. .gitignore
  59. .gn
  60. .mailmap
  61. .rustfmt.toml
  62. .vpython
  63. .vpython3
  64. .yapfignore
  65. AUTHORS
  66. BUILD.gn
  67. CODE_OF_CONDUCT.md
  68. codereview.settings
  69. DEPS
  70. DIR_METADATA
  71. ENG_REVIEW_OWNERS
  72. LICENSE
  73. LICENSE.chromium_os
  74. OWNERS
  75. PRESUBMIT.py
  76. PRESUBMIT_test.py
  77. PRESUBMIT_test_mocks.py
  78. README.md
  79. WATCHLISTS
README.md

Logo Chromium

Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.

The project's web site is https://www.chromium.org.

To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.

Documentation in the source is rooted in docs/README.md.

Learn how to Get Around the Chromium Source Code Directory Structure .

For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.

If you found a bug, please file it at https://crbug.com/new.