From 93be898dbf7c37dc058e7a4060d0e3259318fc5e Mon Sep 17 00:00:00 2001 From: Jeroen van Rijn Date: Wed, 17 Jul 2024 00:54:20 +0200 Subject: [PATCH] Fix typo. --- content/docs/faq.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/faq.md b/content/docs/faq.md index b6123c17..9d7e8127 100644 --- a/content/docs/faq.md +++ b/content/docs/faq.md @@ -401,7 +401,7 @@ a := int(123) ``` ### Why is there no pointer arithmetic? -Type safety and simplicity. Due to slices being a first-class datatype, a lot of the need for pointer arithmetic is reduced. However, if you still require it, the `mem` package provides so utility functions: `mem.ptr_offset` and `mem.ptr_sub`. Odin will allow the programmer to do unsafe things if they so wish. +Type safety and simplicity. Due to slices being a first-class datatype, a lot of the need for pointer arithmetic is reduced. However, if you still require it, the `mem` package provides some utility functions: `mem.ptr_offset` and `mem.ptr_sub`. Odin will allow the programmer to do unsafe things if they so wish. If pointer arithmetic operations are still required and common (maybe due to interfacing with foreign C-like code), [multi-pointers](https://odin-lang.org/docs/overview/#multi-pointers) may be a better option to use.