Skip to content
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

[inductor] Relax type annotations for statically_known_* #126655

Closed
wants to merge 2 commits into from

Conversation

[ghstack-poisoned]
Copy link

pytorch-bot bot commented May 19, 2024

🔗 Helpful Links

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

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 8df6e0c with merge base 6550386 (image):

UNSTABLE - The following job failed but was likely due to flakiness present on trunk and has been marked as unstable:

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

[ghstack-poisoned]
@jansel jansel requested a review from shunting314 May 21, 2024 04:10
Copy link
Contributor

@shunting314 shunting314 left a comment

Choose a reason for hiding this comment

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

Looks good. Just curious why we don't loose the type annotation for the left argument as well?

@jansel
Copy link
Contributor Author

jansel commented May 21, 2024

Looks good. Just curious why we don't loose the type annotation for the left argument as well?

We could, but calling it on (int, int) doesn't make any sense.

@jansel
Copy link
Contributor Author

jansel commented May 21, 2024

@pytorchbot merge

@pytorch-bot pytorch-bot bot added the ciflow/trunk Trigger trunk jobs on your pull request label May 21, 2024
@jansel jansel added topic: not user facing topic category and removed ciflow/trunk Trigger trunk jobs on your pull request labels May 21, 2024
@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

@shunting314
Copy link
Contributor

shunting314 commented May 21, 2024

We could, but calling it on (int, int) doesn't make any sense.

But (int, sympy.Expr) is legit? lol

pytorchmergebot pushed a commit that referenced this pull request May 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants