From c6837a59be798ba73d251a62bbdae8a26b6c5856 Mon Sep 17 00:00:00 2001 From: x0rw Date: Wed, 4 Jun 2025 13:47:51 +0100 Subject: [PATCH] Fix misleading rationale --- src/coding-guidelines/macros.rst | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/coding-guidelines/macros.rst b/src/coding-guidelines/macros.rst index 73322cc5..7094d92f 100644 --- a/src/coding-guidelines/macros.rst +++ b/src/coding-guidelines/macros.rst @@ -108,7 +108,8 @@ Macros :id: rat_M9bp23ctkzQ7 :status: draft - Macros are powerful but they come at the cost of readability, complexity, and maintainability. They obfuscate control flow and type signatures. + Although the compiler reports both the macro expansion and its invocation site, diagnostics originating within macros can be more difficult to interpret than those from ordinary function or type definitions. Complex or deeply nested macros may obscure intent and hinder static analysis, increasing the risk of misinterpretation or overlooked errors during code review. + **Debugging Complexity**