On Fri, Jan 09, 2026 at 12:26:55AM +0100, Marco Elver wrote: > Probably the most idiomatic option is to just factor out construction. > Clearly separating complex object construction from use also helps > readability regardless, esp. where concurrency is involved. We could > document such advice somewhere.
Initializing and locking a mutex (or spinlock, or other primitive) is a not too unusual pattern, often used when inserting an object into a hash table or other lookup data structure. So supporting it without creating pointless wrapper functions would be really useful. One thing that would be nice to have and probably help here is to have lock initializers that create the lock in a held state.
