Check input iterators #107

Closed
dselivanov opened this Issue Jun 19, 2016 · 1 comment

Comments

Projects
None yet
1 participant
@dselivanov
Owner

dselivanov commented Jun 19, 2016

Not reinitialised iterators became the source of numerous issues: #105, #71, #65, #91.
It would be nice to check them on first call of nextElem(). If result will be empty, we should produce sensible warning/error and ask to initialise iterator.

@dselivanov

This comment has been minimized.

Show comment
Hide comment
@dselivanov

dselivanov Jul 21, 2016

Owner

closing this, since I reimplemented iterators with R6. create_* family doesn't modify itoken iterators.

Owner

dselivanov commented Jul 21, 2016

closing this, since I reimplemented iterators with R6. create_* family doesn't modify itoken iterators.

@dselivanov dselivanov closed this Jul 21, 2016

dselivanov added a commit that referenced this issue Oct 3, 2016

dselivanov added a commit that referenced this issue Oct 3, 2016

dselivanov added a commit that referenced this issue Oct 3, 2016

check if input iterator is empty. fixes #107
Former-commit-id: 7e0855854122338084a5ebfad40f9570c6bf30b8 [formerly 0efdb98]
Former-commit-id: ddac82f

dselivanov added a commit that referenced this issue Oct 3, 2016

immutable iterators. Fixes #72, #107, #105, #71, #65, #91, #112
Former-commit-id: 8482b65b0d6258b4b98a574d68f494c3fbb4e3b7 [formerly c7e4947]
Former-commit-id: 146f404
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment