Repository navigation
chore: Enable the C408 lint in ruff - #3362
Merged
Merged
Conversation
|
No actionable comments were generated in the recent review. Summary
Change: Other Merge Risk:
|
Contributor
|
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.
After implementing #3360, I decided to audit our other disabled ruff lints.
C408catches potential performance issues, so should be re-enabled. Dictionary literals have special bytecodes for their construction and may be constant-constructed if all of the keys and values are also immutable constants.dict()can not perform such guarantees (dictitself could be overridden).None of the fixes here are on hot paths (they are mostly in test code), so I don't consider anything here a performance improvement, but having this lint turned on will help us find performance opportunities in the future.