Skip to content

Add transpose to torch/csrc/stable #158160

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

mikaylagawarecki
Copy link
Contributor

@mikaylagawarecki mikaylagawarecki commented Jul 11, 2025

Stack from ghstack (oldest at bottom):

Copy link

pytorch-bot bot commented Jul 11, 2025

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/158160

Note: Links to docs will display an error until the docs builds have been completed.

✅ You can merge normally! (1 Unrelated Failure)

As of commit bdb90cd with merge base 900fba4 (image):

UNSTABLE - The following job is marked as unstable, possibly due to flakiness on trunk:

This comment was automatically generated by Dr. CI and updates every 15 minutes.

mikaylagawarecki added a commit that referenced this pull request Jul 11, 2025
ghstack-source-id: c1a9629
Pull Request resolved: #158160
Copy link
Contributor

@janeyx99 janeyx99 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for getting to this quickly!

One important part of this task (that does not need to be in this PR) is that we should add instructions in the suppress bc lint check to update the stable transpose function here if the API for at::transpose ever changes (otherwise it wouldn't actually be stable)

mikaylagawarecki added a commit that referenced this pull request Jul 16, 2025
ghstack-source-id: a604b08
Pull Request resolved: #158160
mikaylagawarecki added a commit that referenced this pull request Jul 16, 2025
ghstack-source-id: e161870
Pull Request resolved: #158160
Copy link
Contributor

@janeyx99 janeyx99 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! LGTM in approach!

I have a q on how you chose ops.h (does it follow an existing ops.h?) I'm also thinking if we want to have ops.h import from like csrc/stable/transpose.h so people can include all the ops or optionally only include only the ops they use.

@mikaylagawarecki mikaylagawarecki marked this pull request as ready for review July 16, 2025 15:45
@mikaylagawarecki
Copy link
Contributor Author

mikaylagawarecki commented Jul 16, 2025

Ah good point, no I didn't follow any convention in choosing ops.h, where would I look to understand the convention here?

I can move transpose to a separate transpose.h instead

@mikaylagawarecki mikaylagawarecki added release notes: build release notes category topic: new features topic category labels Jul 16, 2025
@mikaylagawarecki
Copy link
Contributor Author

@pytorchbot merge

@pytorch-bot pytorch-bot bot added the ciflow/trunk Trigger trunk jobs on your pull request label Jul 16, 2025
@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged once all checks pass (ETA 0-4 Hours).

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging
Check the merge workflow status
here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ciflow/trunk Trigger trunk jobs on your pull request Merged release notes: build release notes category topic: new features topic category
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy