Lines Matching full:may

30 Most functions in BoringSSL may fail, either due to allocation failures or input
42 queue to determine whether an operation failed. Some codepaths may not interact
43 with the error queue, and the error queue may have state from a previous failed
48 affect the actual behavior of any functions, but may result in errors from both
54 logging. The reason codes are very specific and may change over time.
79 Heap-allocated types may have functioned named like `RSA_new` which allocates a
80 fresh blank `RSA`. Other functions may also return newly-allocated instances.
89 A heap-allocated type may be reference-counted. In this case, a function named
93 compatibility, these functions return `int`, but callers may assume they always
110 types may be allocated on the stack or embedded within another object.
114 initializing a pointer to `NULL`. In this state, the object may not be
135 operations succeeded. More complex C functions may use the `goto err` pattern:
177 These are usually for low-level cryptographic operations. These types may be
202 function call. The function may internally copy information from the argument or
206 A function may instead be documented to *take* or *transfer* ownership of a
208 transfer, no longer owns it. As a corollary, the caller may no longer reference
209 the object without a separate guarantee on the lifetime. The function may even
216 Likewise, output pointers may be owning or non-owning. Unless otherwise
219 lifetime. The pointer may be released when the parent object is released or even
232 API documentation may also describe more complex obligations. For instance, an
233 object may borrow a pointer for longer than the duration of a single function
247 or `EVP_PKEY` which represent keys may typically be used from multiple threads