Lines Matching full:use

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 3. Operator fallback - Developers may use {c:func}`CeedSetOperatorFallbackCeed` to set a {ref}`Ceed…
38 …In order to use operator fallback, the parent backend and fallback backend must use compatible E-v…
55 The `/cpu/self/ref/blocked` backend updates the {ref}`CeedOperator` to use an E-vector and Q-vector…
78 These backends use shared memory to improve performance for the {ref}`CeedBasis` kernels.
91 Ceed backends are free to use any E-vector and Q-vector data layout (including never fully forming …
103 …- If possible, backends should use {c:func}`CeedElemRestrictionSetELayout()` to use the `t2**` tes…
105 …- Backends may choose to use a non-strided E-vector layout; however, the `t2**` tests will not fun…
153 We frequently use comments to document shapes using a lexicographic ordering.
236 8. All libCEED functions must use Doxygen comment blocks before their *definition* (not declaration…
244   @brief Initialize a `Ceed` context to use the specified resource.
248   @param[in]  resource Resource to use, e.g., "/cpu/self"
272 To run on a single file, use
279 ## Include-What-You-Use
281 Header inclusion for source files should follow the principal of 'include what you use' rather than…
284 Please check your code by running the tool [`include-what-you-use`](https://include-what-you-use.or…
285 Most issues reported by `include-what-you-use` should be fixed; however this rule is flexible to ac…
286 …ave `include-what-you-use` installed in a sibling directory to libCEED or set the environment vari…