Ichthyostega
f34ecafa1a
- decision to favour small memory footprint - rather use several Activity records to express invocation - design Activity record as »POD with constructor« - conceptually, Activity is polymorphic, but on implementation level, this is "folded down" into union-based data storage, layering accessor functions on top |
||
|---|---|---|
| .. | ||
| block-flow-test.cpp | ||
| scheduler-activity-test.cpp | ||
| scheduler-commutator-test.cpp | ||
| scheduler-invocation-test.cpp | ||
| scheduler-usage-test.cpp | ||