Lines Matching full:on

20 … are in place and verified correct via tests, then the developer can focus on hardware specific im…
121 If the user calls {c:func}`CeedVectorTakeArray` on the only memory location that contains valid dat…
131   - {c:func}`CeedVectorTakeArray` cannot be called on a vector in a *invalid state*.
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.
204 In general, variable and function names should avoid abbreviations and err on the side of verbosity…
217 …e (for example, `CeedInt`) should be listed on the same line if possible; otherwise, they should b…
237    The block should begin with `/**` and end with `**/`, each on their own line.
272 To run on a single file, use