chromium/src
0
Fork 0
Code Activity

Fix link-breaking typo in unsafe_buffers.md

Browse Source 
Bug: none
Change-Id: Ia3cb33cf49edea7131f47d18d179d8bbd8e069e3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6480478
Commit-Queue: Evan Stade <evanstade@microsoft.com>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Commit-Queue: Tom Sepez <tsepez@chromium.org>
Auto-Submit: Evan Stade <evanstade@microsoft.com>
Cr-Commit-Position: refs/heads/main@{#1450167}
This commit is contained in:
Evan Stade
2025-04-22 13:28:49 -07:00
committed by Chromium LUCI CQ
parent ab95f5d60c
commit 8d390c511a
1 changed files with 2 additions and 2 deletions

4
docs/unsafe_buffers.md

@ -138,13 +138,13 @@ expressions to suppress (see the next section).
### Opting out individual expressions
Individual expressions or blocks of code are opted out by using the
`UNSAFE_BUFFERS()` macro as defined in [`//base/compiler_specific.h`[(../base/compiler_specific.h)
`UNSAFE_BUFFERS()` macro as defined in [`//base/compiler_specific.h`](../base/compiler_specific.h)
file. These should be rare once a project is fully converted, except
perhaps when working with C-style external APIs. These must
always be accompanied by a `// SAFETY:` comment explaining in detail
how the code has been evaluated to be safe for all possible input.
Code introducing UNSAFE_BUFFERS() macro invocations without corresponding
Code introducing `UNSAFE_BUFFERS()` macro invocations without corresponding
`// SAFETY:` comment should be summarily rejected during code review.
To allow for incremental conversion, code can be temporarily opted out by