[Relax] Normalize use of void-type variable to inline R.tuple() #16658
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.
This is a follow-up commit to #16641. While parsing of relax expressions without a variable binding could be implemented at that point (e.g.
R.assert_op(condition)instead ofdummy_var = R.assert_op(condition)), the corresponding printing changes could not. This was because a variable that satisfiesrelax::HasVoidStructInfo(var)could still be used later in the function, and removing its binding would result in use of an undefined variable.This commit normalizes use of void-type variables to an in-line
R.tuple(). This simplifies the relax function, and also allows the binding of void-type variables to be hidden.