Shared iterator consumption

ID: shared-iterator-consumption

Two wrappers referring to the same destructive iterator share its remaining sequence. Their local wrapper fields do not duplicate the underlying consumption state. If one wrapper drains the shared source, a later consumer sees exhaustion. Correct reasoning must therefore track aliases and the actual demand order rather than combine the outputs of imagined independent traversals.

New to topics? Read the docs here!