fvOptions: Changed the source, constraint and correct functions to const

Most fvOptions change the state of the fields and equations they are applied to
but do not change internal state so it makes more sense that the interface is
const, consistent with MeshObjects.  For the few fvOptions which do maintain a
changing state the member data is now mutable.
This commit is contained in:
Henry Weller
2020-08-04 15:40:40 +01:00
parent 87f17b66bb
commit ff20398245
112 changed files with 509 additions and 434 deletions

View File

@ -144,14 +144,14 @@ public:
virtual void correct
(
GeometricField<${TemplateType}, fvPatchField, volMesh>&
);
) const;
//- Explicit and implicit matrix contributions
virtual void addSup
(
fvMatrix<${TemplateType}>& eqn,
const label fieldi
);
) const;
//- Explicit and implicit matrix contributions for compressible
// equations
@ -160,14 +160,14 @@ public:
const volScalarField& rho,
fvMatrix<${TemplateType}>& eqn,
const label fieldi
);
) const;
//- Set value
virtual void constrain
(
fvMatrix<${TemplateType}>& eqn,
const label fieldi
);
) const;
};