Google Git
Sign in
chromium / chromium / src.git / a0464ebf50cfcc9272ff2259f144c5c32b687b9f
commita0464ebf50cfcc9272ff2259f144c5c32b687b9f[log] [tgz]
authorcfredric <[email protected]>Sat Jul 24 01:26:39 2021
committerChromium LUCI CQ <[email protected]>Sat Jul 24 01:26:39 2021
treec4fa3e51c0ea67a149beeb7cf59e81b21f58bba9
parentf0a57a58594c9e2fcf99ab146880ae131360dd4d [diff]
Add BarrierCallback function (analog of BarrierClosure).

There are cases when the results from a few tasks need to be used by a
final "followup" task, similar to the use case of a BarrierClosure, but
where each of the calls to `barrier_closure.Run()` have a result to pass
along. This function provides an easy way of expressing this, instead of
requiring callers to do this plumbing by hand (which is complicated and
repetitive).

In cases where the "results" are coming from off-sequence (e.g. from a
callback passed to PostTaskAndReplyWithResult), this helper should be
more efficient than the naive approach (of repeatedly posting back to
the owning sequence with each result).

Change-Id: I4079296d3300e8c04cbdc81985d4ba4e44facd92
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3043080
Commit-Queue: Chris Fredrickson <[email protected]>
Commit-Queue: Daniel Cheng <[email protected]>
Auto-Submit: Chris Fredrickson <[email protected]>
Reviewed-by: Daniel Cheng <[email protected]>
Reviewed-by: John Delaney <[email protected]>
Reviewed-by: Charlie Harrison <[email protected]>
Cr-Commit-Position: refs/heads/master@{#904986}
3 files changed
tree: c4fa3e51c0ea67a149beeb7cf59e81b21f58bba9
  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. .vpython
  62. .vpython3
  63. .yapfignore
  64. AUTHORS
  65. BUILD.gn
  66. CODE_OF_CONDUCT.md
  67. codereview.settings
  68. DEPS
  69. DIR_METADATA
  70. ENG_REVIEW_OWNERS
  71. LICENSE
  72. LICENSE.chromium_os
  73. OWNERS
  74. PRESUBMIT.py
  75. PRESUBMIT_test.py
  76. PRESUBMIT_test_mocks.py
  77. README.md
  78. 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.