Use at::kLong for torch::tensor(integer_value) when dtype is not specified #29066
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.
Stack from ghstack:
This PR is BC-breaking in the following way:
Previously, C++
torch::tensorwith an integer literal or a braced-init-list ofinteger literals produces a tensor with dtype being the type of the integer literal(s). After this PR, it always produces a tensor of dtype
at::kLong(aka. int64_t), matching Pythontorch.tensorbehavior.Differential Revision: D18307248