Cory Benfield 8423040a9b Mildly rework the NIOLock storage (#2395) ... Motivation: NIOLock uses a storage object constructed from a ManagedBuffer. In general this is fine, but it's a tricky API to use safely and we want to avoid violating any of its guarantees. Modifications: - Store the value in the header and the lock in the elements - Add debug assertions on alignment Result: We'll be a bit more confident of the use of NIOLock		2023-03-27 16:37:09 +01:00
..
NIOAtomic.swift	Remove `#if compiler(>=5.5)` (#2292)	2022-10-13 07:17:46 -07:00
NIOLock.swift	Mildly rework the NIOLock storage (#2395)	2023-03-27 16:37:09 +01:00
NIOLockedValueBox.swift	Tail allocate mutex and a generic value using ManagedBuffer (#2349)	2023-01-17 16:11:10 +00:00
atomics.swift	Deprecate `NIOAtomics` in favor of `Atomics` (#2204)	2022-07-01 02:31:14 -07:00
lock.swift	Remove `#if compiler(>=5.5)` (#2292)	2022-10-13 07:17:46 -07:00