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)
35 lines
1.4 KiB
Groff
35 lines
1.4 KiB
Groff
.TH "serif::dimensions::runtime::RuntimeQuantityValue" 3 "Version v0.0.1a" "SERiF" \" -*- nroff -*-
|
|
.ad l
|
|
.nh
|
|
.SH NAME
|
|
serif::dimensions::runtime::RuntimeQuantityValue \- Runtime resolved type for a quantity value\&. This holds both an ID and a value\&. This is the runtime equivalent to a \fBQuantityValue\fP\&. Note that where these differ is that \fBQuantityValue\fP is built with template types\&. This allows the compiler to resolve it to a plain numeric type and still do optimizations That is generally not the case with \fBRuntimeQuantityValue\fP\&.
|
|
|
|
.SH SYNOPSIS
|
|
.br
|
|
.PP
|
|
.PP
|
|
\fR#include <runtime\&.hpp>\fP
|
|
.SS "Public Attributes"
|
|
|
|
.in +1c
|
|
.ti -1c
|
|
.RI "\fBThermodynamicQuantityID\fP \fBid\fP"
|
|
.br
|
|
.ti -1c
|
|
.RI "double \fBvalue\fP {}"
|
|
.br
|
|
.in -1c
|
|
.SH "Detailed Description"
|
|
.PP
|
|
Runtime resolved type for a quantity value\&. This holds both an ID and a value\&. This is the runtime equivalent to a \fBQuantityValue\fP\&. Note that where these differ is that \fBQuantityValue\fP is built with template types\&. This allows the compiler to resolve it to a plain numeric type and still do optimizations That is generally not the case with \fBRuntimeQuantityValue\fP\&.
|
|
.SH "Member Data Documentation"
|
|
.PP
|
|
.SS "\fBThermodynamicQuantityID\fP serif::dimensions::runtime::RuntimeQuantityValue::id"
|
|
|
|
.SS "double serif::dimensions::runtime::RuntimeQuantityValue::value {}"
|
|
|
|
|
|
.SH "Author"
|
|
.PP
|
|
Generated automatically by Doxygen for SERiF from the source code\&.
|