]> https://gitweb.dealii.org/ - release-papers.git/commitdiff
Distinguish const vs non-const interface 56/head
authorReza Rastak <rastak@stanford.edu>
Sun, 7 Jun 2020 21:56:21 +0000 (14:56 -0700)
committerReza Rastak <rastak@stanford.edu>
Sun, 7 Jun 2020 21:56:21 +0000 (14:56 -0700)
9.2/paper.tex

index f55160a4b5ce00098c10924aa5673aeae7c60305..ec9dd0e0bfd2104ace641e4b7ba265be909af704 100644 (file)
@@ -278,7 +278,8 @@ that we briefly outline in the remainder of this section:
   \item The new \texttt{DiscreteTime} class provides a more
         consistent, more readable, and less error-prone approach to control
         time-stepping algorithms within time-dependent simulations.
-        The interface of this class is designed to be minimal
+        While providing a rich read-only interface, the non-const interface
+        of this class is designed to be minimal
         to enforce a number of important programming invariants, reducing
         the possibility of mistakes in the user code.
         An example is that \texttt{DiscreteTime} ensures that the final time step ends

In the beginning the Universe was created. This has made a lot of people very angry and has been widely regarded as a bad move.

Douglas Adams


Typeset in Trocchi and Trocchi Bold Sans Serif.