gpytorch.module: fix typing annotation #2611
Merged
Conversation
This file contains 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
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
This pull request makes 2 main changes:
I made a mistake in the typing annotations in Add typing annotations to gpytorch.Module #2608, which I am correcting in this pull request. Specifically, I realized that
MutableSet[str]should beMutableSet[Prior]. This pull request fixes this mistake.I updated the typing annotation for the
setting_closureto have no return type (i.e., it returns None) to better match how setting closures are actually used throughout the GPyTorch codebase and examples. Previously,setting_closurewas annotated with a "Self" return type, but the return value ofsetting_closureis never used anywhere in the GPyTorch codebase.