Improve type stability of cat_pullback#610
Merged
Merged
Conversation
Member
|
This seems fine to me. Could you add something like this example as a test? The rules for hcat and vcat have a similar branch, |
Contributor
Author
It also doesn't matter for 1 and 2D inputs here, which is why I suspect union splitting is bailing out. Cthulhu shows 4 variants of |
76c6caa to
ce98fd4
Compare
mcabbott
approved these changes
Apr 26, 2022
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.
Currently,
ChainRules.jl/src/rulesets/Base/array.jl
Lines 356 to 362 in 8c34f19
Tuple{Union{UnitRange{Int64}, Colon}, ...}. When the number of input dims >=3, this appears to fail some union-splitting threshold forgetindexon certain array types. Here's a MWE with FillArrays, which Zygote uses somewhat extensively:This PR resolves the instability by always creating a
UnitRange. However, I am not sure if this is sufficiently semantically close toColonto pass muster, so RFC :) .