Lines Matching full:safety

61     /// # Safety
69         // INVARIANT: By the safety requirements of this function, invariants are upheld.
70         // SAFETY: By the safety requirement of this function, we own a
81     /// # Safety
86         // SAFETY: By type invariant, `self.0` is a valid `struct request` and
127         // SAFETY: By type invariant, `this.0` was a valid `struct request`. The
150         // SAFETY: By type invariant, `self.0` is a valid `struct request`
152             // SAFETY: We released a refcount above that we can reclaim here.
161     /// # Safety
167         // SAFETY: By safety requirements for this function, `this` is a
171         // SAFETY: By C API contract, `wrapper_ptr` points to a valid allocation
179         // SAFETY: By type invariant, `self.0` is a valid allocation. Further,
209     /// # Safety
213         // SAFETY: Because of the safety requirements of this function, the
219 // SAFETY: Exclusive access is thread-safe for `Request`. `Request` has no `&mut
224 // SAFETY: Shared access is thread-safe for `Request`. `&self` methods that
228 // SAFETY: All instances of `Request<T>` are reference counted. This
238         // SAFETY: The type invariants of `ARef` guarantee that `obj` is valid
241         // SAFETY: The type invariant of `Request` guarantees that the private