Updated Coding Style (markdown)

2023-10-03 05:15:32 +03:00 · 2023-10-03 05:15:32 +03:00 · 83976a213e
parent c2e3f88862
commit 83976a213e
1 changed files with 1 additions and 0 deletions
--- a/Coding-Style.md
+++ b/Coding-Style.md
@ -17,6 +17,7 @@ We recommend to follow these guidelines when writing code for RPCS3. They aren't
 * Ensure that every source file you modify has the newline at the end of file. Every line ends with "newline" and the end of file must have "newline" too, GitHub usually warns about it.
 * Use brackets around multi-term ternary operator conditions especially if they occur with other code on the same line. `(x * y) + ((a > b)? c : d)` is more readable than `x * y + a > b? c : d`.
 * Use `ensure()` and `fmt::throw_exception()` in order to add asserts in your code.
+* Avoid recursive locking, there are always better alternatives.

 ***
 ### Emulator coding style