[go: nahoru, domu]

Reland "[mojo] Better import header includes"

This is a reland of aefd23ef161e0fadfb493e506cd127047681f137

Max token count for content_browser_client.cc is bumped up here
because we exceed the previous limit after fixing some IWYU
issues.

Original change's description:
> [mojo] Better import header includes
>
> There are two problems addressed here:
>
>  - Forward headers were unnecessarily including extra (i.e. traits)
>    public headers; but fixing that revealed a second problem:
>  - The logic to decide whether a transitive import requires a full
>    header or only a forward header was incorrect.
>
> So this fixes the logic which decides whether to import with a full
> header or forward header, and it removes the inclusion of public traits
> headers from forward headers.
>
> Also fixes tons of IWYU and forward declaration deficiencies
> revealed by these changes.
>
> Fixed: 1111156
> Change-Id: I181b62c605581a1f303f07257471277d178e9e06
> Tbr: tsepez@chromium.org
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2375889
> Reviewed-by: Tom Sepez <tsepez@chromium.org>
> Reviewed-by: Kenneth Russell <kbr@chromium.org>
> Reviewed-by: Ilya Sherman <isherman@chromium.org>
> Reviewed-by: Yuwei Huang <yuweih@chromium.org>
> Reviewed-by: Eric Roman <eroman@chromium.org>
> Reviewed-by: Avi Drissman <avi@chromium.org>
> Reviewed-by: Oksana Zhuravlova <oksamyt@chromium.org>
> Reviewed-by: Kentaro Hara <haraken@chromium.org>
> Reviewed-by: Matt Falkenhagen <falken@chromium.org>
> Commit-Queue: Ken Rockot <rockot@google.com>
> Auto-Submit: Ken Rockot <rockot@google.com>
> Cr-Commit-Position: refs/heads/master@{#802479}

Tbr: avi@chromium.org
Tbr: falken@chromium.org
Tbr: eroman@chromium.org
Tbr: isherman@chromium.org
Tbr: kbr@chromium.org
Tbr: oksamyt@chromium.org
Tbr: tsepez@chromium.org
Tbr: yuweih@chromium.org
Change-Id: I59deaa2648377be499d10326155eb5f55273f8f1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2381733
Reviewed-by: Avi Drissman <avi@chromium.org>
Reviewed-by: Oksana Zhuravlova <oksamyt@chromium.org>
Reviewed-by: Yuwei Huang <yuweih@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Commit-Queue: Ken Rockot <rockot@google.com>
Cr-Commit-Position: refs/heads/master@{#803246}
53 files changed
tree: 6a4ee3a04c490e9685f1ec8061e26c62e2bdf565
  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. components/
  14. content/
  15. courgette/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia/
  22. gin/
  23. google_apis/
  24. google_update/
  25. gpu/
  26. headless/
  27. infra/
  28. ios/
  29. ipc/
  30. jingle/
  31. media/
  32. mojo/
  33. native_client_sdk/
  34. net/
  35. pdf/
  36. ppapi/
  37. printing/
  38. remoting/
  39. rlz/
  40. sandbox/
  41. services/
  42. skia/
  43. sql/
  44. storage/
  45. styleguide/
  46. testing/
  47. third_party/
  48. tools/
  49. ui/
  50. url/
  51. weblayer/
  52. .clang-format
  53. .clang-tidy
  54. .eslintrc.js
  55. .git-blame-ignore-revs
  56. .gitattributes
  57. .gitignore
  58. .gn
  59. .vpython
  60. .vpython3
  61. .yapfignore
  62. AUTHORS
  63. BUILD.gn
  64. CODE_OF_CONDUCT.md
  65. codereview.settings
  66. DEPS
  67. DIR_METADATA
  68. ENG_REVIEW_OWNERS
  69. LICENSE
  70. LICENSE.chromium_os
  71. OWNERS
  72. PRESUBMIT.py
  73. PRESUBMIT_test.py
  74. PRESUBMIT_test_mocks.py
  75. README.md
  76. 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.

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.