add tests for the output types of prototype functional dispatchers #7118
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
vfdev-5
approved these changes
Jan 20, 2023
facebook-github-bot
pushed a commit
that referenced
this pull request
Jan 24, 2023
…tchers (#7118) Reviewed By: YosuaMichael Differential Revision: D42706904 fbshipit-source-id: 6f5da4914fd5d30cf6ef575ce6a1266e2012157b
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Addresses #7113 (comment). Contrary to my believe, we currently don't have any automated tests that enforce that the output type of a dispatcher is the same as the input type. This PR corrects that.
cc @vfdev-5 @bjuncek