commit | a6da8151aad4fd638a8229c29625557a265cccd9 | [log] [tgz] |
---|---|---|
author | Tom Sepez <tsepez@chromium.org> | Wed Aug 21 23:13:17 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Aug 21 23:13:17 2024 |
tree | e3b94d0e9f1fd9474d1808cd655dec0f67c3bb00 | |
parent | f12d12e00faeb0b10a7ed667cbcea03a33726c75 [diff] |
Spanify GifFileWriter::WriteBuffer() Its sole caller already is making a span for us. Then use helper functions for spans to avoid unsafe buffer usage. Change-Id: I2a435f4be9b8d88ad82aec67732f2da4e8b4dea4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5800787 Commit-Queue: Tom Sepez <tsepez@chromium.org> Reviewed-by: Ahmed Fakhry <afakhry@chromium.org> Cr-Commit-Position: refs/heads/main@{#1345132}
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.