-
Notifications
You must be signed in to change notification settings - Fork 295
Allow derived coord references to be lazy. #6517
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
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #6517 +/- ##
=======================================
Coverage 89.89% 89.89%
=======================================
Files 90 90
Lines 24138 24138
Branches 4492 4492
=======================================
Hits 21699 21699
Misses 1679 1679
Partials 760 760 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
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.
@pp-mo Awesome! Thanks for doing this 💯
Add a whatsnew entry then we can bank this just in time for 3.13 👍
⏱️ Performance Benchmark Report: d69b0a7Performance shifts
Full benchmark results
Generated by GHA run |
Noticed during testing for #6404, and implementing solution #6515
The old code used
src.data
when attaching a reference surface to a factory, but clearlysrc.core_data()
makes a lot more sense, as a factory generally represents a "lazy" calculation anyway.Although worth considering a separate issue, I want to test this alongside a completed #6515 + be merged into that when it's clear it doesn't break it.
Hence WIP : intend to merge into #6515 when ready