Note for now much of the docs is LLM written. This was done to save time and focus on code development. The docs have been LOOSLEY reviewed. However, the code itself has been either fully written by hand or fully reviewed. Therefore, the docs should at the moment be seen as a loose resource rather than authoratiative (and this is on top of the general ability for docs to drift)
38 lines
1.2 KiB
Groff
38 lines
1.2 KiB
Groff
.TH "serif::discretization::forms::IsOperation" 3 "Version v0.0.1a" "SERiF" \" -*- nroff -*-
|
|
.ad l
|
|
.nh
|
|
.SH NAME
|
|
serif::discretization::forms::IsOperation
|
|
.SH SYNOPSIS
|
|
.br
|
|
.PP
|
|
.PP
|
|
\fR#include <operands\&.hpp>\fP
|
|
.SH "Concept definition"
|
|
.PP
|
|
|
|
.nf
|
|
template<typename OperationCandidate>
|
|
concept serif::discretization::forms::IsOperation =
|
|
std::same_as<std::remove_cvref_t<OperationCandidate>, Operation::Value> ||
|
|
std::same_as<std::remove_cvref_t<OperationCandidate>, Operation::Gradient> ||
|
|
std::same_as<std::remove_cvref_t<OperationCandidate>, Operation::Divergence> ||
|
|
std::same_as<std::remove_cvref_t<OperationCandidate>, Operation::Curl> ||
|
|
std::same_as<std::remove_cvref_t<OperationCandidate>, Operation::NormalTrace>
|
|
.PP
|
|
.fi
|
|
.SH "Detailed Description"
|
|
.PP
|
|
@breif Concept to validate that sone type is a valid operation, if you extend \fBOperation\fP you should extend this concept\&.
|
|
|
|
.PP
|
|
\fBTodo\fP
|
|
.RS 4
|
|
Could C++26 reflection make keeping this and Operation parallel easier / more automatic since this code would live in the same translation unit?
|
|
.RE
|
|
.PP
|
|
|
|
.SH "Author"
|
|
.PP
|
|
Generated automatically by Doxygen for SERiF from the source code\&.
|