-
Notifications
You must be signed in to change notification settings - Fork 200
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
Disable caching for inline calculations #1872
Disable caching for inline calculations #1872
Conversation
84b0cc1
to
1ee37b9
Compare
Makes sense to me - @sphuber do you agree? |
Codecov Report
@@ Coverage Diff @@
## develop #1872 +/- ##
==========================================
+ Coverage 61.38% 66.7% +5.31%
==========================================
Files 320 320
Lines 32549 33420 +871
==========================================
+ Hits 19981 22293 +2312
+ Misses 12568 11127 -1441
Continue to review full report at Codecov.
|
We had some more discussion at #1871, but I'm not sure what the conclusion is. |
Just that I wasn't sure of the exact reason for it breaking and I wanted to investigate it better but sadly I forgot a bit about it. I would be ok with merging this, but we should maybe open another issue to investigate the caching of function calculations. |
1ee37b9
to
c7ad8ae
Compare
c7ad8ae
to
d0166c2
Compare
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.
Approving this, since the actual problem is fixed in develop
which will become v1.0.0
once released
Fixes #1871
Caching on inline calculations was broken since the switch to using the
workfunction
for their implementation, although unfortunately in a way that was not caught by the tests (see #1871).Since caching isn't implemented for the
workfunction
, there is not immediate way to fix this. It's probably possible, but will work correctly only if the user adheres to the design rules for inline calcs, for example to not rely on some external parameter in the calculation.Given all this, and the fact that inline calcs are supposed to be very fast operations anyway, the best course of action right now seems to me to just disable caching for the
InlineCalculation
.