Hi All, I propose preventing SupplyingBarriers from running inside repeat(). SupplyingBarriers, of which SideEffectCapStep is currently the only implementation, are similar to ReducingBarriers in that they consume all starts and supply a single traverser to the next Step.
This consumption process destroys the loop information that serves as a terminating condition for many repeat traversals. To prevent user errors, we should prevent SupplyingBarriers from being used inside repeat in the StandardVerificationStrategy like it is for ReducingBarriers. Does anyone have any thoughts regarding this? Thanks, Ken
