-
Notifications
You must be signed in to change notification settings - Fork 119
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
Only use nrn_prop_datum_alloc
.
#2683
Conversation
I'm unable to find the associated |
Quality Gate passedKudos, no new issues were introduced! 0 New issues |
✔️ e701266 -> Azure artifacts URL |
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## master #2683 +/- ##
==========================================
+ Coverage 66.18% 66.32% +0.13%
==========================================
Files 559 559
Lines 108940 108657 -283
==========================================
- Hits 72107 72064 -43
+ Misses 36833 36593 -240 ☔ View full report in Codecov by Sentry. |
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.
Looks good to me.
The aim of this refactoring is to make
nrn_prop_datum_alloc
the only function that allocates datums (forProp
; I'm not 100% sure about Datums in general).I've attached a diagram of what I think is currently how
prop.dparam
is allocated and freed. There's still one alternative path remaining, via the global variablenrn_point_prop_
. However, I suspect this will naturally go away when we store the datums inside the SoA.