On 2026-07-30 14:09, Luca Boccassi wrote:
There's nothing a developer needs to do, as it's completely self-contained and transparent - it's not like it's creating or managing threads, it's just an internal spinlock. In a single-threaded caller it's a no-op.
Not if there are signal handlers.
the library works exactly as it always did. Its internals are its own
Sure, but callers in general should know that the library maintains shared global state and so there can be races if the app is multithreaded and even some problems regardless of whether it's multithreaded. For experts in the library this is obvious; for non-experts, it's not. I am thinking more of the latter case.
