When we transform a plan, all clocks appear to implicitly start at 0. At least there is no obvious way to specify any other value. But during plan execution, clocks may well have been running for a while before the transformation, so to have the most correct and powerful semantics, we should have a way to supply clock states with the transformation input.
When we transform a plan, all clocks appear to implicitly start at 0. At least there is no obvious way to specify any other value. But during plan execution, clocks may well have been running for a while before the transformation, so to have the most correct and powerful semantics, we should have a way to supply clock states with the transformation input.