diff options
| author | Kai Köhne <kai.koehne@qt.io> | 2025-07-04 17:05:36 +0200 |
|---|---|---|
| committer | Kai Köhne <kai.koehne@qt.io> | 2025-07-07 20:54:03 +0200 |
| commit | c59adf5a3a4950e2fed5e60e3b3d316281c9f918 (patch) | |
| tree | 73029651cb3f350beb300a4f4b5df4c3e61a0138 /src/network/socket/qnativesocketengine_unix.cpp | |
| parent | 11f2d3c86f41f0f05de0a74cf16166c4487a72a2 (diff) | |
Doc: Remove deadlock warnings in most QMutex documentation
The origin of this sentence predates the Qt 5 history. Anyhow, as is,
the sentence is too general, as locking the same mutex
over time from the same thread is definitely supported, as long as
it is also unlocked every time. Furthermore, for the tryLock()
variants, the thread will only dead-lock if an infinite wait time
is specified.
Improve the sentence for QMutex::lock(), but just leave out this
information for the other methods. The behavior is arguably as you
would expect it from a mutex.
Pick-to: 6.9 6.10
Change-Id: I0b658cc29c2f2d2cd6b59d49e2baa285508ec720
Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>
Diffstat (limited to 'src/network/socket/qnativesocketengine_unix.cpp')
0 files changed, 0 insertions, 0 deletions