Support Tensor source for x.set_(storage, offset, size, strides)#77007
Support Tensor source for x.set_(storage, offset, size, strides)#77007ezyang wants to merge 1 commit intogh/ezyang/1145/basefrom
Conversation
This is convenient for cases where we don't have Storage bound correctly (e.g., meta tensors). It is also consistent with a universe where we get rid of storages, although arguably this is never gonna happen. Signed-off-by: Edward Z. Yang <ezyang@fb.com> [ghstack-poisoned]
🔗 Helpful links
✅ No Failures (0 Pending)As of commit c174dbe (more details on the Dr. CI page): Expand to see more💚 💚 Looks good so far! There are no failures yet. 💚 💚 This comment was automatically generated by Dr. CI (expand for details).Please report bugs/suggestions to the (internal) Dr. CI Users group. |
|
@pytorchbot merge this |
|
Hey @ezyang. |
) Summary: This is convenient for cases where we don't have Storage bound correctly (e.g., meta tensors). It is also consistent with a universe where we get rid of storages, although arguably this is never gonna happen. Signed-off-by: Edward Z. Yang <ezyangfb.com> Pull Request resolved: #77007 Approved by: https://github.com/ngimel Test Plan: contbuild & OSS CI, see https://hud.pytorch.org/commit/pytorch/pytorch/e3dcd175f7aacb6aa2fb150b01335afd508c9d52 Reviewed By: malfet Differential Revision: D36250486 fbshipit-source-id: ccc70c69df10fe915a185a0cb365a48944033a0e
Stack from ghstack:
This is convenient for cases where we don't have Storage bound
correctly (e.g., meta tensors). It is also consistent with a universe
where we get rid of storages, although arguably this is never
gonna happen.
Signed-off-by: Edward Z. Yang ezyang@fb.com