ABSTRACT
In the last two chapters, I dragged you through the internal workings of the Quantum Framework (QF). The way the QF is coded internally resembles the construction of a bridge over turbulent waters, and at times, it is like balancing on the edge of a cliff without a safety net. Virtually every line of code, as with every step on a tightrope, poses risks. Are all possible scenarios of preemptions taken into account? Are all sensitive code fragments protected with critical sections? Are the critical sections short enough? Are priority inversions ruled out? Is the framework code watertight? Well, I sure hope so,1 but this is neither productive nor the fun way of developing
software: it’s hard, it’s slow, it’s risky — it’s the conventional approach to multithreaded programming. However, the struggle is over. The bridge is now open for traffic, so everybody can cross it quickly and comfortably, without taking much risk.
