Searched refs:unwrapping (Results 1 – 20 of 20) sorted by relevance
11 NIST KW init #2 unwrapping AES-128: OK66 NIST KW lengths #15 KW unwrapping output buffer too short69 NIST KW lengths #16 KWP unwrapping output buffer too short87 NIST KW lengths #15 KW unwrapping output NULL90 NIST KW lengths #16 KWP unwrapping output NULL
548 JsonDeserializer<Object> unwrapping = orig.unwrappingDeserializer(xform); in resolve() local549 if (unwrapping != orig && unwrapping != null) { in resolve()550 prop = prop.withValueDeserializer(unwrapping); in resolve()
94 * [Element wrapping / unwrapping limitations](#wrapping)115 ### Element wrapping / unwrapping limitations <a id="wrapping"></a>
46 To see which type the `Response` holds you pattern match on the variant unwrapping the underlying v…
203 (like unwrapping on `None` or out-of-range indexing) or for early development stages
98 wrapping and unwrapping helpers, common handle operations, and utilities for
697 without unwrapping its ``__wrapped__`` chain. ``globalns`` and1111 as its sole argument that allows the unwrapping to be terminated early if1114 :func:`signature` uses this to stop unwrapping if any object in the
120 * Contributed #381: Allow inlining/unwrapping of value from single-component JSON array
1595 #381: Allow inlining/unwrapping of value from single-component JSON array2094 wrapping/unwrapping settings
105 `3146 <https://wg21.link/LWG3146>`__,"Excessive unwrapping in ``std::ref/cref``","October 2021","|C…
99 …link/LWG2697>`__","[concurr.ts] Behavior of ``future/shared_future``\ unwrapping constructor when…
564 The situation looks nearly identical for wrapping and unwrapping Windows handles
2436 * Support unwrapping of nested metadata (e.g. ID3 and SCTE-35 in EMSG).
2249 * Support unwrapping of nested metadata (e.g. ID3 and SCTE-35 in EMSG).
2658 - spirv: Do more complex unwrapping in get_nir_type
4215 $x{unwrapping → ənræpɪŋ ; # ənræppɪŋ ənwræpɪŋ
205154 unwrapping %11761 ənrˈæpɪŋ
171429 unwrapping %24037 ənrˈæpɪŋ