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)
31 lines
1.0 KiB
Groff
31 lines
1.0 KiB
Groff
.TH "serif::discretization::domain::BoundaryIDResolver< BoundaryT, BoundaryIDListT >" 3 "Version v0.0.1a" "SERiF" \" -*- nroff -*-
|
|
.ad l
|
|
.nh
|
|
.SH NAME
|
|
serif::discretization::domain::BoundaryIDResolver< BoundaryT, BoundaryIDListT > \- A specialization of the \fBDomainIDResolver\fP struct for a \fBDomainOrSet\fP type\&. This struct is used to resolve the domain IDs for a given \fBDomainOrSet\fP type\&.
|
|
|
|
.SH SYNOPSIS
|
|
.br
|
|
.PP
|
|
.SH "Detailed Description"
|
|
.PP
|
|
|
|
.SS "template<typename BoundaryT, typename BoundaryIDListT>
|
|
.br
|
|
struct serif::discretization::domain::BoundaryIDResolver< BoundaryT, BoundaryIDListT >"A specialization of the \fBDomainIDResolver\fP struct for a \fBDomainOrSet\fP type\&. This struct is used to resolve the domain IDs for a given \fBDomainOrSet\fP type\&.
|
|
|
|
|
|
.PP
|
|
\fBTemplate Parameters\fP
|
|
.RS 4
|
|
\fIDomainT\fP The \fBDomainOrSet\fP type to resolve the IDs for\&.
|
|
.br
|
|
\fIDomainIDTs\fP The list of DomainID types that are expected in the mesh\&.
|
|
.RE
|
|
.PP
|
|
|
|
|
|
.SH "Author"
|
|
.PP
|
|
Generated automatically by Doxygen for SERiF from the source code\&.
|