[BugFix] Fix Binary reshaping #3084
Merged
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.
Description
Fixes a bug introduced by #3077 where shapes for newly instantiated
Binaryspecs are incompatible with the value ofnpassed.In particular the following pattern is used in
unsqueezeand other shape-modifying operations:However, this is wrong because we should extract
nfrom the newshaperather than from the currentself.shape.We fix by switching to check on the new
shape:Motivation and Context
Without this change, we have value errors raised due to shape mismatches:
NOTE: I have tried to include a test to check for this, but I don't know if that is the correct place and scope.
Types of changes
What types of changes does your code introduce? Remove all that do not apply:
Checklist
Go over all the following points, and put an
xin all the boxes that apply.If you are unsure about any of these, don't hesitate to ask. We are here to help!