Fix squeeze offset for sliced views - #2933
Open
Tyagiquamar wants to merge 1 commit into
Open
Tyagiquamar wants to merge 1 commit into
Tyagiquamar wants to merge 1 commit into
Conversation
This branch has not been deployed
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.
Squeezing a sliced view now retains its data offset instead of reading from the start of the underlying tensor. Both squeeze overloads reuse the existing offset helper; expressions without a data interface keep their zero-offset fallback.
Fixes #2834.
Validation in Docker (Ubuntu 24.04, clang 18.1.3, C++20): the added regression failed before the fix with
{1,2}instead of{2,3}. After the fix, the focused squeeze tests passed in both row-major and column-major configurations (2 test cases, 12 assertions each). The modified header and test passedclang-format-18 --dry-run --Werror.