Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Check input iterators #107

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

Check input iterators #107

dselivanov opened this issue Jun 19, 2016 · 1 comment
Assignees
Labels
Milestone

Comments

@dselivanov
Copy link
Owner

@dselivanov 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
Copy link
Owner Author

@dselivanov 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
Former-commit-id: 7e0855854122338084a5ebfad40f9570c6bf30b8 [formerly 0efdb98]
Former-commit-id: ddac82f
dselivanov added a commit that referenced this issue Oct 3, 2016
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
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.