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.
Description
I propose a solution to the infinite recursion problem.
The idea is to keep track of what is being computed with a local function.
If the current tensordict encounters itself down the line, it register what key it is and lets that aside for the moment. Once the computation is "finished" (with all the nested tensordicts let aside) it fills the keys one at a time with what has been retrieved.
Albeit the logic is repetitive i did not find a way of recycling the code across methods (
all
,clone
,to_tensordict
,expand
etc)IMO it would be better to have sort of a decorator to handle that, but I can't really think of a way to make it work in the general case.
Any idea @Zooll or @tcbegley ?