""""""""""""""""""""
- Some features are missing in the Maestro future implementation
- (`simgrid::kernel::Future`, `simgrid::kernel::Promise`)
- could be extended to support additional features:
- `when_any`, `shared_future`, etc.
+ (`simgrid::kernel::Future`, `simgrid::kernel::Promise`)
+ could be extended to support additional features:
+ `when_any`, `shared_future`, etc.
- The corresponding feature might then be implemented in the user process
futures (`simgrid::simix::Future`).
.. _howto_churn:
Modeling Churn (e.g., in P2P)
-****************************
+*****************************
One of the biggest challenges in P2P settings is to cope with the
churn, meaning that resources keep appearing and disappearing. In
enable it unless you really want to formally verify your applications:
SimGrid is slower and maybe less robust when MC is enabled.
- - **Failed assert**
+ - **Failing assert**
In this example, two actors send some data to a central server,
which asserts that the messages are always received in the same order.
This is obviously wrong, and the model-checker correctly finds a
counter-example to that assertion.
- |br| `examples/s4u/mc-failed-assert/s4u-mc-failed-assert.cpp <https://framagit.org/simgrid/simgrid/tree/master/examples/s4u/mc-failed-assert/s4u-mc-failed-assert.cpp>`_
+ |br| `examples/s4u/mc-failing-assert/s4u-mc-failing-assert.cpp <https://framagit.org/simgrid/simgrid/tree/master/examples/s4u/mc-failing-assert/s4u-mc-failing-assert.cpp>`_
.. |br| raw:: html
Comm() : Activity() {}
public:
+#ifndef DOXYGEN
friend XBT_PUBLIC void intrusive_ptr_release(Comm* c);
friend XBT_PUBLIC void intrusive_ptr_add_ref(Comm* c);
friend Mailbox; // Factory of comms
+#endif
virtual ~Comm();