That sounds both familiar and weird, like some strange lazy collection that performs an I/O operation to hydrate every time it creates iterator.

Whatever it is, it's certainly not something that would justify a modification of standard API to cover this use case.