Lines Matching refs:func

13 …er creates the backend implementation of the specific method and calls {c:func}`CeedSetBackendFunc…
27 1. Delegation - Developers may use {c:func}`CeedSetDelegate` to set a general delegate {ref}`Ceed` …
31 2. Object delegation  - Developers may use {c:func}`CeedSetObjectDelegate` to set a delegate {ref}`…
35 …func}`CeedSetOperatorFallbackCeed` to set a {ref}`Ceed` object to provide any unimplemented {ref}`…
103 …- If possible, backends should use {c:func}`CeedElemRestrictionSetELayout()` to use the `t2**` tes…
121 If the user calls {c:func}`CeedVectorTakeArray` on the only memory location that contains valid dat…
122 …the user must set valid data by calling {c:func}`CeedVectorSetValue`, {c:func}`CeedVectorSetArray`…
129 …o borrowed memory is set with {c:func}`CeedVectorSetArray` with `copy_mode = CEED_USE_POINTER` and…
130 …st call {c:func}`CeedVectorSetArray` with `copy_mode = CEED_USE_POINTER` for the appropriate preci…
131   - {c:func}`CeedVectorTakeArray` cannot be called on a vector in a *invalid state*.
135 …- Owned memory can be allocated by calling {c:func}`CeedVectorSetValue` or by calling {c:func}`Cee…
136 …- Owned memory can be set by calling {c:func}`CeedVectorSetArray` with `copy_mode = CEED_OWN_POINT…
137   - Owned memory can also be allocated by calling {c:func}`CeedVectorGetArrayWrite`.
142 …- Internal synchronization and user calls to {c:func}`CeedVectorSync` cannot be made on a vector i…
143 …- Calls to {c:func}`CeedVectorGetArray` and {c:func}`CeedVectorGetArrayRead` cannot be made on a v…
144 …- Calls to {c:func}`CeedVectorSetArray` and {c:func}`CeedVectorSetValue` can be made on a vector i…
145   - Calls to {c:func}`CeedVectorGetArrayWrite` can be made on a vector in an *invalid* state.
146 …Data synchronization is not required for the memory location returned by {c:func}`CeedVectorGetArr…
147 …The caller should assume that all data at the memory location returned by {c:func}`CeedVectorGetAr…