commit | 2f2615d47ac182c0eeb0597356cc0a559ae83c8d | [log] [tgz] |
---|---|---|
author | Tomasz Wiszkowski <ender@google.com> | Thu Sep 26 21:56:02 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Sep 26 21:56:02 2024 |
tree | 132533375fc84a7cdb4f207b8048a5d251405587 | |
parent | f7528e711be1e2831198547aa45ebc3402d81bff [diff] |
Drop C-style arrays from generated structs TLDR: Change replaces the following fields in structs generated from JSON: - const TYPE* array_name - size_t array_name_size with - const base::span<const TYPE> array_name and removes some unsafe buffer usage warning suppression pragmas. This change proposes replacing pointer-and-length struct fields with their base::span<> equivalent. The change does not entirely abandon the C-style structs, but hides and abstracts them so that iterating elements no longer causes unsafe buffer usage errors. The change addresses C-style arrays in structs only, and does not solve the equivalent case of generated collections encompassing all JSON elements (such as `kAllEngines`). For that reason many pragma statements could not be removed yet. Bug: b/40285824, b/352691908 Change-Id: I32820f62eedb241926f5b47af778d61158ac627c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5888845 Reviewed-by: James Cook <jamescook@chromium.org> Commit-Queue: Tomasz Wiszkowski <ender@google.com> Reviewed-by: Mark Pearson <mpearson@chromium.org> Reviewed-by: Calder Kitagawa <ckitagawa@chromium.org> Cr-Commit-Position: refs/heads/main@{#1360785}
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.