Add support for nested #each
#31
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
snichme
approved these changes
Dec 9, 2025
spuun
added a commit
that referenced
this pull request
Dec 9, 2025
#31 introduced a bug where an method call triggering an iteration raised an error. This happened if e.g. a delete had been done before the iteration.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Because
#eachcalls#rewindon the underlying IO it wasn't possible to nest each calls, because the inner#eachwill ruin the position for the outer one.This PR change so position is restored to what it was before
#eachwas called. This is also added other read methods doing iterations such as#any?and#all?.