Add SendValidation tag/attribute to Mojo

This change adds a new mojo tag/attribute to make it easier to debug
validation errors on serialization in the case where there's developer
error. This takes advantage of the mojo Feature infrastructure to flip
the validation error on when the feature is on.

```
The tag can be added like so:
feature kBarValidationFeature {
  const string name = "BarValidationFeature";
  const bool default_state = true;
};

interface Foo {
  [SendValidation=kBarValidationFeature]
  Bar(Struct struct_needing_validation);
};
```

This change adds unit tests in mojo_unittests.

As a part of this change, another set of serialization templates were
added to facilitate a smaller binary size. If SendValidation is
requested, the alternative template is used. If no SendValidation
specialization exists, then the code will automatically fall back to the
original serialization.

The compile size is greatly expanded because this adds a
new serialization path to every Struct, Union, Array, and Map used by
Mojo. A follow-up change reduces increase down to about 0.45% compile
size increase with additional complexity.

Compile-size: See commit description.
Bug: 400895804
Change-Id: Idb0c4daeb179e938ea4c9e195f6c95f0e45c8f04
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6328899
Reviewed-by: Alex Gough <ajgo@chromium.org>
Commit-Queue: Emily Andrews <emiled@microsoft.com>
Reviewed-by: Fred Shih <ffred@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1457638}
43 files changed
tree: 491f2fddf0de504ad65a1cf2cc8e56b4d44c7f54
  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. codelabs/
  13. components/
  14. content/
  15. crypto/
  16. dbus/
  17. device/
  18. docs/
  19. extensions/
  20. fuchsia_web/
  21. gin/
  22. google_apis/
  23. gpu/
  24. headless/
  25. infra/
  26. ios/
  27. ipc/
  28. media/
  29. mojo/
  30. native_client_sdk/
  31. net/
  32. pdf/
  33. ppapi/
  34. printing/
  35. remoting/
  36. rlz/
  37. sandbox/
  38. services/
  39. skia/
  40. sql/
  41. storage/
  42. styleguide/
  43. testing/
  44. third_party/
  45. tools/
  46. ui/
  47. url/
  48. webkit/
  49. .clang-format
  50. .clang-tidy
  51. .clangd
  52. .git-blame-ignore-revs
  53. .gitallowed
  54. .gitattributes
  55. .gitignore
  56. .gitmodules
  57. .gn
  58. .mailmap
  59. .rustfmt.toml
  60. .vpython3
  61. .yapfignore
  62. ATL_OWNERS
  63. AUTHORS
  64. BUILD.gn
  65. CODE_OF_CONDUCT.md
  66. codereview.settings
  67. CPPLINT.cfg
  68. CRYPTO_OWNERS
  69. DEPS
  70. DIR_METADATA
  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.