Improve Warning Suppression Performance by Using set
#1932
Merged
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
This PR optimizes the way warning suppression is handled by changing
_no_warn_slugsfrom alistto aset. This improves performance when checking if a warning should be suppressed, reducing lookup complexity from O(n) to O(1) on average. Additionally, using asetensures uniqueness, preventing duplicate warning slugs from being added.Changes
list[str]withset[str]for_no_warn_slugs.set(self.config.disable_warnings)..append(slug)with.add(slug)to maintain set behavior.Why?