Replace PropertyDescriptor with properties#3125
Merged
Conversation
|
Performance benchmarks:
|
Member
|
Either the current |
Member
Author
|
Yes they are purely internal. As you can see, they don't show up in the |
EwoutH
approved these changes
Jan 13, 2026
Member
EwoutH
left a comment
There was a problem hiding this comment.
Thanks! Looks good.
If you can post any benchmark numbers I think that would be great to have as historical reference.
Member
Author
|
See #3113 for some numbers on performance. |
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.
This PR replaces the
PropertyDescriptorwith normal properties using a property factory pattern. This PR follows up on a suggestion from @codebreaker32 in #3080. It roughly halves the access time to a property in a cell.Implementation details
property()function to assign getters and setters for a property to a cell.layer.databy wrapping it in property. The setter is most critical here because it ensures thatself._datais never changed to a different NumPy array, thereby breaking the properties assigned via step 1.