llvmbot wrote:

<!--LLVM PR SUMMARY COMMENT-->

@llvm/pr-subscribers-clang

Author: Louis Dionne (ldionne)

<details>
<summary>Changes</summary>

That missing space was causing the whole sentence to be rendered incorrectly in 
the resulting HTML.

---
Full diff: https://github.com/llvm/llvm-project/pull/107905.diff


1 Files Affected:

- (modified) clang/include/clang/Basic/AttrDocs.td (+1-1) 


``````````diff
diff --git a/clang/include/clang/Basic/AttrDocs.td 
b/clang/include/clang/Basic/AttrDocs.td
index 546e5100b79dd9..cc9bc499c9cc24 100644
--- a/clang/include/clang/Basic/AttrDocs.td
+++ b/clang/include/clang/Basic/AttrDocs.td
@@ -6849,7 +6849,7 @@ def UnsafeBufferUsageDocs : Documentation {
 The attribute ``[[clang::unsafe_buffer_usage]]`` should be placed on functions
 that need to be avoided as they are prone to buffer overflows or unsafe buffer
 struct fields. It is designed to work together with the off-by-default compiler
-warning ``-Wunsafe-buffer-usage``to help codebases transition away from raw 
pointer
+warning ``-Wunsafe-buffer-usage`` to help codebases transition away from raw 
pointer
 based buffer management, in favor of safer abstractions such as C++20 
``std::span``.
 The attribute causes ``-Wunsafe-buffer-usage`` to warn on every use of the 
function or
 the field it is attached to, and it may also lead to emission of automatic 
fix-it

``````````

</details>


https://github.com/llvm/llvm-project/pull/107905
_______________________________________________
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

Reply via email to