[tensor wrapper subclass] Add trace transform for tensor subclasses #1584
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.
What does this PR do?
Implement
my_subclass.__tensor_flatten__
andMySubclass.__tensor_unflatten__
MySubclass.__torch_dispatch__
.torch.fx
to understand the extended behavior. Currently the mapping from core aten ops to thunder.torch ops is quite optimistic; just querying the aten op name tothunder.torch
.Since
__torch_dispatch__
extends the behavior that is implemented in C++ level, we'd need to apply the transform to split forward and backward traces separately.