Add a 2 and 3 arity version of zip #10
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
phausler
requested review from
jmschonfeld,
kperryua,
natecook1000,
parkera and
timvermeulen
kperryua
approved these changes
Jan 18, 2022
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.
Zip can utilize task groups; which reduce the burden of task cancellation slightly from the alternate parity versions (like combining the latest value into a tuple instead of awaiting all members for a tuple). This implementation rests heavily on the inout method for iterating which transacts upon writing back to optionals to complete the zip tuple. Other approaches are totally value ways (like for example making a state machine tuple transition from each satisfaction to another) however the optional based approach leans heavier onto the built-in type safety of Swift's type resolution.