the attempt to integrate additional deadline and significance parameters unveils a design problem due to the layering of contexts - the Activity-Language attempts to abstract away the ''Scheduler mechanics'' - but this implementation logic now needs to pass additional parameters - and notably there is the possibility of direct re-scheduling from within the Activity-Dispatch The symptom of this problem is that it's no longer possible to implement the ExecutionCtx.post() function in the real Scheduler-context |
||
|---|---|---|
| .. | ||
| activity-detector-test.cpp | ||
| activity-detector.hpp | ||
| block-flow-test.cpp | ||
| scheduler-activity-test.cpp | ||
| scheduler-commutator-test.cpp | ||
| scheduler-invocation-test.cpp | ||
| scheduler-load-control-test.cpp | ||
| scheduler-service-test.cpp | ||
| scheduler-stress-test.cpp | ||
| scheduler-usage-test.cpp | ||
| work-force-test.cpp | ||