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
a freed block until there is no blocks pointing to it anymore using some
sort of basic garbage-collector.
-@subsubsection contributing_todo_state_hashing Hasing the states
+@subsubsection contributing_todo_state_hashing Hashing the states
In order to speed up the state comparison an idea was to create a hash of the
state. Only states with the same hash would need to be compared using the