Only check that arguments are Variables in VariableType #4943
Conversation
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
Don't check the ScalarType and Backend of arguments in VariableType. Instead, only check that arguments are Variables of any type. The precise type checks are handled by the base type. Many of our functions take heterogeneous types. There isn't enough information in Declarations.yaml to ensure the precise types of arguments in VariableType, which makes it difficult to add new methods.
gchanan
approved these changes
Jan 30, 2018
| } | ||
|
|
||
| Tensor & VariableType::unpack_any(const Tensor & t, const char * name, int pos) const { | ||
| Variable & VariableType::checked_cast(const Tensor & t, const char * name, int pos) { |
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry, something went wrong.
soumith
pushed a commit
that referenced
this pull request
Jan 31, 2018
* Revert "Clarify grad_input_mask documentation in derivatives.yaml (#4963)" This reverts commit 6f3266b. * Revert "fix triu and tril for zero-strided inputs on gpu (#4962)" This reverts commit 6c197c2. * Revert "Add mutex for CPU RNG and move TH to C++ (#4041)" This reverts commit 96239dd. * Revert "Support multivariate TransformedDistributions (#4937)" This reverts commit ca5071d. * Revert "Only check that arguments are Variables in VariableType (#4943)" This reverts commit d444379. * Revert "torch.set_num_threads sets MKL option too (#4949)" This reverts commit 2aaeec0.
colesbury
added a commit
that referenced
this pull request
Feb 1, 2018
colesbury
added a commit
that referenced
this pull request
Feb 1, 2018
Don't check the ScalarType and Backend of arguments in VariableType. Instead, only check that arguments are Variables of any type. The precise type checks are handled by the base type. Many of our functions take heterogeneous types. There isn't enough information in Declarations.yaml to ensure the precise types of arguments in VariableType, which makes it difficult to add new methods. This is #4943 with a fix to the memset call
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Don't check the ScalarType and Backend of arguments in VariableType.
Instead, only check that arguments are Variables of any type. The
precise type checks are handled by the base type.
Many of our functions take heterogeneous types. There isn't enough
information in Declarations.yaml to ensure the precise types of
arguments in VariableType, which makes it difficult to add new methods.