...which just turns the pipeline into exhausted state, instead of raising an Assertion failure The point is, expandChildren() does not guard itself, since it _requires_ an non-empty iterator as precondition. Thus, any function downstream, which invokes expandChildren(), has to check and guard this call apropriately. In the concrete case at hand we just stop adding further constraints when the pipeline is already in exhausted state |
||
|---|---|---|
| .. | ||
| draw | ||
| DIR_INFO | ||
| empty.html | ||
| InterfaceConcept_Varga.mm | ||
| renderengine.html | ||
| thinkPad.ichthyo.mm | ||
| uml | ||
| workflow.mm | ||