fix: fromArray now actually uses the provided shape parameter - #27
Merged
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 PR fixes a bug where
fromArray()silently ignored its$shapeparameter.Motivation and Context
fromArray()accepts an optional$shapeparameter but delegated toarray(), which always infers shape from the input data. CallingNDArray::fromArray([1, 2, 3, 4, 5, 6], [2, 3])would create a 1D array of shape[6]instead of the requested[2, 3], with no warning or error.What's Changed
fromArray()now duplicatesarray()'s creation logic instead of proxying to it, using the provided shape when given and only inferring from data as a fallbackBreaking Changes
None.