From 8eed1ebf9ca2532fac255708a8dc418378c78b0a Mon Sep 17 00:00:00 2001
From: Boris Kolpackov <boris@codesynthesis.com>
Date: Wed, 8 Feb 2017 10:22:01 +0200
Subject: Get rid of count_postponed

Terget execution is postponed with regards to the current thread only thus
it doesn't seem right to make postponed a target state.
---
 build2/operation.cxx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to 'build2/operation.cxx')

diff --git a/build2/operation.cxx b/build2/operation.cxx
index f37d642..ea9a462 100644
--- a/build2/operation.cxx
+++ b/build2/operation.cxx
@@ -168,10 +168,10 @@ namespace build2
         }
       case target_state::changed:
         break;
-      case target_state::postponed:
-        assert (false);
       case target_state::failed:
         //@@ MT: This could probably happen in a parallel build.
+        //       Or does state() throw? Do we want to print?
+        break;
       default:
         assert (false);
       }
-- 
cgit v1.1