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

Iterator #do:, use #nextPresent #522

Merged
merged 1 commit into from
Nov 23, 2023
Merged

Conversation

MarcusDenker
Copy link
Contributor

@MarcusDenker MarcusDenker commented Nov 23, 2023

Another small refactoring to reduce isRemoved calls.

#do: uses next, but we have #nextPresent that handles removed values

closes #360 (but I added a new issue as #nextPresent has to restore values)

#do: uses next, but we have #nextPresent that handles removed values

closes #360 (
@noha noha merged commit dcc0cfc into main Nov 23, 2023
2 checks passed
@MarcusDenker MarcusDenker deleted the Iterator-use-nextPresent-in-do branch November 23, 2023 14:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

Iterator>>#do uses isRemoved but should use restoreValue
2 participants