From c515da9f3710ea765b99b179470866f9ca411aaa Mon Sep 17 00:00:00 2001
From: Patrick Pelissier <patrick.pelissier@gmail.com>
Date: Wed, 29 Mar 2023 22:50:51 +0200
Subject: [PATCH] Update documentation

---
 README.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/README.md b/README.md
index c6d23c52..132b2576 100644
--- a/README.md
+++ b/README.md
@@ -1012,6 +1012,10 @@ your compiler. There are often completely useless and misleading:
 * For GCC, uses -ftrack-macro-expansion=0
 * For CLANG, uses -fmacro-backtrace-limit=1
 
+Due to the unfortunate [weak](https://en.wikipedia.org/wiki/Strong_and_weak_typing#Pointers) nature of the C language for pointers,
+you should turn incompatible pointer type warning into an error in your compiler.
+For GCC / CLANG, uses -Werror=incompatible-pointer-types
+
 
 Benchmarks
 ----------