Add explicit None return annotations to void method#3555
Open
mshsheikh wants to merge 1 commit into
Open
Conversation
##Summary - This PR adds explicit `-> None` return annotations to methods that do not return a value. - It improves readability, makes the intent of these methods clearer, and keeps the code consistent with the rest of the file. - It also helps static type checkers and IDEs understand the code better. - This change does not affect runtime behavior. ##Why This improves type clarity and keeps the codebase consistent for static analysis. It does not change runtime behavior.
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
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.
Summary
-> Nonereturn annotations to methods that do not return a value.Why
This improves type clarity and keeps the codebase consistent for static analysis. It does not change runtime behavior.