From: Gabriel Corona <gabriel.corona@loria.fr>
Date: Fri, 22 Jul 2016 12:12:39 +0000 (+0200)
Subject: [doc] TODO -1 timeout should not be forever
X-Git-Tag: v3_14~735^2
X-Git-Url: http://info.iut-bm.univ-fcomte.fr/pub/gitweb/simgrid.git/commitdiff_plain/03277f5f1a9bea432bc946551e9eaeca4844d6d3

[doc] TODO -1 timeout should not be forever
---

diff --git a/doc/doxygen/community_giveback.doc b/doc/doxygen/community_giveback.doc
index 8eee215fbd..cc428d0004 100644
--- a/doc/doxygen/community_giveback.doc
+++ b/doc/doxygen/community_giveback.doc
@@ -147,6 +147,11 @@ Some support for C++11-style time/duration is implemented (see `chrono.hpp`)
 but only available in some (S4U) APIs. It would be nice to add support for
 them in the rest of the C++ code.
 
+A related change would be to avoid using "-1" to mean "forever" at least in S4U
+and in the internal code. For compatibility, MSG should probably keep this
+semantic. We should probably always use separate functions
+(`wait` vs `wait_for`).
+
 @subsubsection contributing_todo_futures Futures
 
  - Some features are missing in the Maestro future implementation