You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to make CowRepr implement DataOwned, where DataOwned is changed to mean "a storage type which can own its data". The only issue is the .into_shared() method, which says, "Turn the array into a shared ownership (copy on write) array, without any copying." We can't always turn a CowArray into an ArcArray without copying. One approach (which would be a breaking change) would be to remove DataOwned::into_shared and just rely on this From implementation instead. Then, we could implement DataOwned for CowRepr without issues.
Regardless of the CowRepr stuff, this impl still seems useful.
Agree. I hope to keep the into_shared etc methods somehow, but it's clear that they need to change to support wider diversity of owned arrays (including future differences in allocator). Maybe adding a Clone bound to into_shared() would be ok and sufficient, and then the specific From impls can be used by users when they need to avoid Clone requirements.
Maybe adding a Clone bound to into_shared() would be ok and sufficient, and then the specific From impls can be used by users when they need to avoid Clone requirements.
Yeah, I think this makes the most sense. We'd move into_shared from DataOwned to Data, add an A: Clone bound, and drop the "without any copying" guarantee. In most cases, the user would just use .into_shared() to convert arrays to ArcArray (so that all they'd need is are A: Clone and S: Data bounds), but if they want to create an ArcArray from an array without A: Clone, they would use an Into<ArcArray> bound instead.
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
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.
I'd like to make
CowReprimplementDataOwned, whereDataOwnedis changed to mean "a storage type which can own its data". The only issue is the.into_shared()method, which says, "Turn the array into a shared ownership (copy on write) array, without any copying." We can't always turn aCowArrayinto anArcArraywithout copying. One approach (which would be a breaking change) would be to removeDataOwned::into_sharedand just rely on thisFromimplementation instead. Then, we could implementDataOwnedforCowReprwithout issues.Regardless of the
CowReprstuff, this impl still seems useful.