From dab6fb58e47980d77a6da7151e528f04c246d2fa Mon Sep 17 00:00:00 2001 From: Karol Lewandowski Date: Mon, 24 Feb 2025 11:26:10 +0100 Subject: [PATCH] threading_model.md: Mention that writing is prioritized over reading --- .../basics/architectural_overview/threading/threading_model.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/topics/basics/architectural_overview/threading/threading_model.md b/topics/basics/architectural_overview/threading/threading_model.md index 5686aae17..0b69e118a 100644 --- a/topics/basics/architectural_overview/threading/threading_model.md +++ b/topics/basics/architectural_overview/threading/threading_model.md @@ -127,6 +127,8 @@ The described lock characteristics conclude the following: - multiple threads can read data at the same time - once a thread acquires the write lock, no other threads can read or write data +Note that acquiring write locks is prioritized over read locks. + Acquiring and releasing locks explicitly in code would be verbose and error-prone and must never be done by plugins. The IntelliJ Platform enables write intent lock implicitly on EDT (see [](#locks-and-edt) for details) and provides an [API for accessing data under read or write locks](#accessing-data).