Zip with next #217
Open
Zip with next #217
Conversation
This file contains 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
|
Hello - My apologies, but this PR has been open for several weeks and I can't move forward until after this PR Is processed. |
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.
This PR adds the
zip_with_nextfunction, which zips together adjacent elements, or seq[0:-1] with seq[1:].Its functionality is common (think of how many algorithms require processing adjacent elements together), therefore it makes sense to include it in Pyfunctional's API and not leave it to clients to add it as an @extend function.
Kotlin's collections API already has this function, and adding it to Pyfunctional makes it even more serviceable and versatile.