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
Generate type match guard for torch.Size input #96421
Conversation
I suppose hypothetically, if the user code ends up working polymorphically over the SizeVariable, in such a way that a tuple would work, this type match is not necessary. But we do not carefully test for this. Signed-off-by: Edward Z. Yang <ezyang@meta.com> [ghstack-poisoned]
I suppose hypothetically, if the user code ends up working polymorphically over the SizeVariable, in such a way that a tuple would work, this type match is not necessary. But we do not carefully test for this. Signed-off-by: Edward Z. Yang <ezyangmeta.com> ghstack-source-id: 625fafae308bb794dee147cf2bca246e68b86ae7 Pull Request resolved: #96421
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/96421
Note: Links to docs will display an error until the docs builds have been completed. ❌ 1 FailuresAs of commit 3c5fa0e: This comment was automatically generated by Dr. CI and updates every 15 minutes. |
I suppose hypothetically, if the user code ends up working polymorphically over the SizeVariable, in such a way that a tuple would work, this type match is not necessary. But we do not carefully test for this. Signed-off-by: Edward Z. Yang <ezyangmeta.com> cc soumith voznesenskym penguinwu anijain2305 EikanWang jgong5 Guobing-Chen XiaobingSuper zhuhaozhe blzheng Xia-Weiwen wenzhe-nrv jiayisunx desertfire [ghstack-poisoned]
I suppose hypothetically, if the user code ends up working polymorphically over the SizeVariable, in such a way that a tuple would work, this type match is not necessary. But we do not carefully test for this. Signed-off-by: Edward Z. Yang <ezyangmeta.com> ghstack-source-id: 887c96920f948942a1bb8d4f21eec81f87759a2a Pull Request resolved: #96421
I suppose hypothetically, if the user code ends up working polymorphically over the SizeVariable, in such a way that a tuple would work, this type match is not necessary. But we do not carefully test for this. Signed-off-by: Edward Z. Yang <ezyangmeta.com> cc soumith voznesenskym penguinwu anijain2305 EikanWang jgong5 Guobing-Chen XiaobingSuper zhuhaozhe blzheng Xia-Weiwen wenzhe-nrv jiayisunx desertfire [ghstack-poisoned]
I suppose hypothetically, if the user code ends up working polymorphically over the SizeVariable, in such a way that a tuple would work, this type match is not necessary. But we do not carefully test for this. Signed-off-by: Edward Z. Yang <ezyangmeta.com> cc soumith voznesenskym penguinwu anijain2305 EikanWang jgong5 Guobing-Chen XiaobingSuper zhuhaozhe blzheng Xia-Weiwen wenzhe-nrv jiayisunx desertfire [ghstack-poisoned]
I suppose hypothetically, if the user code ends up working polymorphically over the SizeVariable, in such a way that a tuple would work, this type match is not necessary. But we do not carefully test for this. Signed-off-by: Edward Z. Yang <ezyangmeta.com> ghstack-source-id: 09218eda684a9321839032db0984ab9e50166513 Pull Request resolved: #96421
@pytorchbot merge |
Merge failedReason: This PR needs a label If not, please add the For more information, see Details for Dev Infra teamRaised by workflow job |
@pytorchbot merge -f "unrelated jinja problem" |
Merge startedYour change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
I suppose hypothetically, if the user code ends up working polymorphically over the SizeVariable, in such a way that a tuple would work, this type match is not necessary. But we do not carefully test for this. Signed-off-by: Edward Z. Yang <ezyang@meta.com> Pull Request resolved: pytorch/pytorch#96421 Approved by: https://github.com/jansel, https://github.com/voznesenskym
I suppose hypothetically, if the user code ends up working polymorphically over the SizeVariable, in such a way that a tuple would work, this type match is not necessary. But we do not carefully test for this. Signed-off-by: Edward Z. Yang <ezyang@meta.com> Pull Request resolved: pytorch/pytorch#96421 Approved by: https://github.com/jansel, https://github.com/voznesenskym
Stack from ghstack (oldest at bottom):
I suppose hypothetically, if the user code ends up working
polymorphically over the SizeVariable, in such a way that a tuple would
work, this type match is not necessary. But we do not carefully test
for this.
Signed-off-by: Edward Z. Yang ezyang@meta.com
cc @soumith @voznesenskym @penguinwu @anijain2305 @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @Xia-Weiwen @wenzhe-nrv @jiayisunx @desertfire