...turns out there is still a lot of leeway in the possible implementation, and seemingly it is too early to decide which case to consider the default. Thus I'll proceed with the drafted preliminary solution... - on primary-chain, an inhibited Gate dispatches itself into future for re-check - on Notification, activation happens if and only if this very notification opens the Gate - provide a specifically wired requireDirectActivation() to allow enforcing a minimal start time |
||
|---|---|---|
| .. | ||
| activity-detector-test.cpp | ||
| activity-detector.hpp | ||
| block-flow-test.cpp | ||
| scheduler-activity-test.cpp | ||
| scheduler-commutator-test.cpp | ||
| scheduler-invocation-test.cpp | ||
| scheduler-usage-test.cpp | ||