From bec642525c90f33b76c9794416d7e1b467c1cbd3 Mon Sep 17 00:00:00 2001
From: Mattes D <github@xoft.cz>
Date: Tue, 17 Sep 2019 13:49:17 +0200
Subject: [PATCH] Clarify spaces vs unary operator

---
 CONTRIBUTING.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 7a1d85a05..662a2bbb0 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -29,9 +29,10 @@ Here are the conventions:
    - `Foo(Vector3d a_Param1, const cCuboid & a_Param2)`
    - See the discussion in issue #3853
  - Put spaces after commas. `Vector3d(1, 2, 3)` instead of `Vector3d(1,2,3)`
- - Put spaces before and after every operator.
+ - Put spaces before and after every operator, except unary operators.
    - `a = b + c;`
    - `if (a == b)`
+   - `++itr`
  - Keep individual functions spaced out by 5 empty lines, this enhances readability and makes navigation in the source file easier.
  - Add those extra parentheses to conditions, especially in C++:
    - `if ((a == 1) && ((b == 2) || (c == 3)))` instead of ambiguous `if (a == 1 && b == 2 || c == 3)`