WIP: Implements owning_iter method
#35
Open
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
This method might be used to iterate over the owned value producing new OwningRef'erences.
|
Any updates? This would be useful for creating an |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 method might be used to iterate over the owned value producing new
OwningRef'erences. I don't see any other way to produce multiple OwningRefs by iterating over something (except calling
mapfor every element of a sequence, which works fine for slices but not for mappings or other more complex iterators).Current pull request lacks docstring. But more important thing is whether it's memory safe. I'm not sure I'm doing everything 100% right.
Thoughts?