RFC: Expose xnew in C_wrapper, maintaining compat - #322
Conversation
Codecov Report
@@ Coverage Diff @@
## master #322 +/- ##
==========================================
+ Coverage 87.80% 88.07% +0.27%
==========================================
Files 3 3
Lines 697 713 +16
==========================================
+ Hits 612 628 +16
Misses 85 85
Continue to review full report at Codecov.
|
|
@sohailrreddy are you still interested in this? If not, I will close. From #313 (comment):
|
|
Closing as stale. I understand the reasoning for this, so if anyone has a benchmark where this makes a difference in practice, please post a comment and we can re-open the PR. |
|
Hello. Exposing xnew could really be useful for us. The reason is that our methods to compute objective, grad and constraint values all need to compute some shared data first, and then use that shared data. If For example, if Right now we are using our own fork of the package to do this, but I think it could be update this PR and merge it. I can do the PR if needed. |
|
I don't see why this can't be achieved with a closure? Please open a PR with your changes if you would like to discuss. |
Replacement for #313, just so I can try it out. I don't know if we should merge this. The alternative is for the user to write a closure, which isn't that much work.
cc @sohailrreddy