-
-
Notifications
You must be signed in to change notification settings - Fork 32
Improved performance of chords creation for a specific key by creating functions instead of creating them on init #52
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
Merged
aure
merged 3 commits into
AudioKit:main
from
SebastianBoldt:fixes/changes-to-Key-Type-for-faster-computations
Jun 3, 2025
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I strongly recommend that these utility functions live outside the actual implementation of
Key-- as these functions are not directly related to the actual data structure, they should live in a file called like Key+Extensions as they are utility/connivence functionsThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Honestly, I'm unsure about proceeding with this because the overall style of the project typically consolidates all related business logic into a single file. Particularly considering that the functions for initially populating these values were also included in the same file, I would prefer to keep them where they are.
I transformed them from actual functions into computed variables; perhaps this is an improvement.
If you'd still like me to transfer them to a file, I can certainly do that. I don't mind at all.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hmmm you are right, we probably need to have some style opinion, as that is mine, I like spectating nice utility functions into
...+Extensionsfiles. Your additions LGTM and don't actually impact the underlying data structure so we should be good.