Preserve custom AbstractArray types during broadcasting of ArrayPartition - #136
Merged
Merged
Conversation
…to decide naturally which style it is
Member
|
This is great! Thanks! |
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
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.
It would be useful to allow a custom AbstractArray type inside an ArrayPartition to be preserved during broadcasting, but currently it is not. Understandably, one needs to extend some of the broadcasting functions to the new type, as I show below. However, there is a small fix needed to the package to enable this. This is because
unpack, which strips out each partition one by one and creates a separateBroadcastedwrapper for it, gives the same promotedBroadcastStyleto each one, even if they are different types, so some get dispatched to the wrongsimilarfunction incopy. In the PR, I don't pass theStyleduring the unpack to allow it to decide naturally which style it is.If you'd like further detail, for example, consider
and then I define
and calculate
The
MyTypewrapper is converted to just aVector{Float64}No problem. We haven't extended
similarfor theBroadcastedwrapper to do anything for our new type, so it just falls back to the default. So we endow it with someBroadcastStylefunctionality:Except that now,
produces an error, because our new
similarfunction gets called on the nonMyTypepart of theArrayPartition, too. The PR fixes this.