From 6f4a6e1db7c6feaabf7fe1883b588cf1b328cae9 Mon Sep 17 00:00:00 2001 From: Jannik Silvanus Date: Mon, 21 Aug 2023 08:18:52 +0200 Subject: [PATCH] [Docs] Fix typo in opaque pointers doc --- llvm/docs/OpaquePointers.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/llvm/docs/OpaquePointers.rst b/llvm/docs/OpaquePointers.rst index a51042fa01d6..aecbe1ec6bb9 100644 --- a/llvm/docs/OpaquePointers.rst +++ b/llvm/docs/OpaquePointers.rst @@ -180,7 +180,7 @@ While direct usage of pointer element types is immediately apparent in code, there is a more subtle issue that opaque pointers need to contend with: A lot of code assumes that pointer equality also implies that the used load/store type or GEP source element type is the same. Consider the following examples -with typed an opaque pointers: +with typed and opaque pointers: .. code-block:: llvm