-
Notifications
You must be signed in to change notification settings - Fork 26.3k
Move scalar boolean to THTensor, rename scalar in this context to zer… #9783
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
…o dim. Manifest: 1) The scalar boolean is now in THTensor, although it isn't hooked up at the TH level yet. 2) setScalar is gone, everything now goes through the maybeScalar equivalent (which is renamed) 3) all "scalars" in this context now refer to "zero_dim" in order to differentiate this concept from the "Scalar" class.
facebook-github-bot
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@gchanan has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.
aten/src/TH/THTensor.hpp
Outdated
| std::vector<int64_t> sizes_; | ||
| std::vector<int64_t> strides_; | ||
|
|
||
| // TODO: get rid of this, use the sizes_/strides_ .size() instead |
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry, something went wrong.
|
New comment: |
facebook-github-bot
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@gchanan has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.
facebook-github-bot
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@gchanan has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.
|
@pytorchbot retest this please |
…… (#9783) Summary: …o dim. Manifest: 1) The scalar boolean is now in THTensor, although it isn't hooked up at the TH level yet. 2) setScalar is gone, everything now goes through the maybeScalar equivalent (which is renamed) 3) all "scalars" in this context now refer to "zero_dim" in order to differentiate this concept from the "Scalar" class. Pull Request resolved: pytorch/pytorch#9783 Differential Revision: D8978911 Pulled By: gchanan fbshipit-source-id: f09254be4bebad0e4c510fefe4158b4f7e92efe1
pytorch#9783) Summary: …o dim. Manifest: 1) The scalar boolean is now in THTensor, although it isn't hooked up at the TH level yet. 2) setScalar is gone, everything now goes through the maybeScalar equivalent (which is renamed) 3) all "scalars" in this context now refer to "zero_dim" in order to differentiate this concept from the "Scalar" class. Pull Request resolved: pytorch#9783 Differential Revision: D8978911 Pulled By: gchanan fbshipit-source-id: f09254be4bebad0e4c510fefe4158b4f7e92efe1
pytorch#9783) Summary: …o dim. Manifest: 1) The scalar boolean is now in THTensor, although it isn't hooked up at the TH level yet. 2) setScalar is gone, everything now goes through the maybeScalar equivalent (which is renamed) 3) all "scalars" in this context now refer to "zero_dim" in order to differentiate this concept from the "Scalar" class. Pull Request resolved: pytorch#9783 Differential Revision: D8978911 Pulled By: gchanan fbshipit-source-id: f09254be4bebad0e4c510fefe4158b4f7e92efe1
…o dim.
Manifest: