lmi-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lmi-commits] [lmi] master 620dfec 03/11: Don't test good() explicitly


From: Greg Chicares
Subject: [lmi-commits] [lmi] master 620dfec 03/11: Don't test good() explicitly
Date: Thu, 1 Jul 2021 20:19:03 -0400 (EDT)

branch: master
commit 620dfec43d3928e7c37cdce9b5c42c712d57e83b
Author: Gregory W. Chicares <gchicares@sbcglobal.net>
Commit: Gregory W. Chicares <gchicares@sbcglobal.net>

    Don't test good() explicitly
    
    Inserters begin by constructing a sentry object that tests good().
    There's no good reason to test it explicitly.
---
 zero.hpp | 17 +++++++----------
 1 file changed, 7 insertions(+), 10 deletions(-)

diff --git a/zero.hpp b/zero.hpp
index e954768..416374f 100644
--- a/zero.hpp
+++ b/zero.hpp
@@ -70,16 +70,13 @@ inline void expatiate
     ,double                   fx
     )
 {
-    if(os_trace.good())
-        {
-        os_trace
-            << "iteration " << n_iter
-            << " "          << "IBLQb"[technique]
-            << " iterand "  << x
-            << " value "    << fx
-            << std::endl
-            ;
-        }
+    os_trace
+        << "iteration " << n_iter
+        << " "          << "IBLQb"[technique]
+        << " iterand "  << x
+        << " value "    << fx
+        << std::endl
+        ;
 }
 } // namespace detail
 



reply via email to

[Prev in Thread] Current Thread [Next in Thread]