doc: Move mutex and thread section into guideline section
What the developer wrote
Authored by MarcoFalke
doc: Move mutex and thread section into guideline section
Previously, they have been in the "Tips and tricks" section, which seems a bit off.
What changed, and why it matters
This commit is a pure documentation reorganization. It moves the 'Locking/mutex usage notes' and 'Threads' sections from the 'Tips and tricks' area into a new 'Development guidelines' section in the developer notes. No code, logic, or security behavior changed.
No action required. This is a non-functional documentation change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff only reorders Markdown headings in doc/developer-notes.md. It inserts a ‘# Development guidelines’ heading before the existing ‘## Locking/mutex usage notes’ and ‘## Threads’ subsections, and removes the same heading from its previous location before ‘## General Bitcoin Core’. There are no code changes.
Changed components
doc/developer-notes.mdInspect captured patch +5 / −5
diff --git a/doc/developer-notes.md b/doc/developer-notes.md
index 94b33632..4a4841cb 100644
--- a/doc/developer-notes.md
+++ b/doc/developer-notes.md
@@ -671,6 +671,11 @@ Additional resources:
* [GCC Instrumentation Options](https://gcc.gnu.org/onlinedocs/gcc/Instrumentation-Options.html)
* [Google Sanitizers Wiki](https://github.com/google/sanitizers/wiki)
+# Development guidelines
+
+A few non-style-related recommendations for developers, as well as points to
+pay attention to for reviewers of Bitcoin Core code.
+
## Locking/mutex usage notes
The code is multi-threaded and uses mutexes and the
@@ -740,11 +745,6 @@ and its `cs_KeyStore` lock for example).
- [ThreadI2PAcceptIncoming (`b-i2paccept`)](https://doxygen.bitcoincore.org/class_c_connman.html#a57787b4f9ac847d24065fbb0dd6e70f8)
: Listens for and accepts incoming I2P connections through the I2P SAM proxy.
-# Development guidelines
-
-A few non-style-related recommendations for developers, as well as points to
-pay attention to for reviewers of Bitcoin Core code.
-
## General Bitcoin Core
- New features should be exposed on RPC first, then can be made available in the GUI.
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.