Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clean up ScancodeWrapper #2170

Closed

Conversation

zoldalma999
Copy link
Member

Back when PurityLake added errors to ScancodeWrapper's iter functions, I noticed that the code for the class is repetitive at places, and could be cleaned up. So I did it (about 3 months ago, and then never made a pr out of it). Technically this implementation should also be faster at creating the object as well, but since this is a small optimization, it is not like this is going to speed up anything significantly. Accessing times should be around the same though (again, not that it matter much).

@zoldalma999 zoldalma999 requested a review from a team as a code owner May 17, 2023 13:57
@zoldalma999 zoldalma999 force-pushed the scancodewrapper-cleanup branch from 2c160f0 to 92f5628 Compare May 18, 2023 09:54
@yunline yunline added Code quality/robustness Code quality and resilience to changes key pygame.key labels Jun 4, 2023
@zoldalma999
Copy link
Member Author

I'll be closing this for now, but I do plan to reopen something like this in the future. I will, however, definitely wait for #1912 to be merged.

@zoldalma999 zoldalma999 deleted the scancodewrapper-cleanup branch July 1, 2023 17:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Code quality/robustness Code quality and resilience to changes key pygame.key
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants