Lines Matching full:requirement

55 // requirement of `AtomicType`.
141     // SAFETY: Per the safety requirement of `AtomicType`, `T` is round-trip transmutable to
151     // SAFETY: Per the safety requirement of the function, the transmute operation is sound.
158         // INVARIANT: Per the safety requirement of `AtomicType`, `into_repr(v)` is a valid `T`.
173     ///   accesses are atomic, then this safety requirement is trivially fulfilled.
219         // SAFETY: Per function safety requirement, `ptr` is a valid pointer and the object will
220         // live long enough. It's safe to return a `&Atomic<T>` because function safety requirement
257         // CAST: `T` and `T::Repr` has the same size and alignment per the safety requirement of
532         // INVARIANT: `self.0` is a valid `T` after `atomic_add()` due to safety requirement of
564         // INVARIANT: `self.0` is a valid `T` after `atomic_fetch_add*()` due to safety requirement
607         // INVARIANT: `self.0` is a valid `T` after `atomic_fetch_sub*()` due to safety requirement
769     // SAFETY: Per the function safety requirement, `ptr` is valid and aligned to
796     // SAFETY: Per the function safety requirement, `ptr` is valid and aligned to
820     // SAFETY: Per the function safety requirement, `ptr` is valid and aligned to
846     // SAFETY: Per the function safety requirement, `ptr` is valid and aligned to