Normalize multi dim list in indexing #56893
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.
PR types
Breaking changes
PR changes
APIs
Description
Pcard-66985
Background Information:
1. Semantic of List/Tensor and Tuple: In indexing, the semantics of
List
type is same withTensor/Array
type (corresponding to one axis). As a comparison,Tuple
type is different (corresponding to multiple axes, each element is an index on the corresponding axis).2. The current semantic of List are contradictory:Currently in Paddle,
List
type have two semantics.Tensor/Array
, which is naturally).[]
is equivalent to tuple,which is to wrap indexes on different axes together).What this PR did
This PR unified the semantics of
List
in indexing, like Numpy(as described in #51466 ). From this PR,List
is same withTensor/Array
in any case.