Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #3970 +/- ##
===========================================
- Coverage 100.00% 99.25% -0.75%
===========================================
Files 43 43
Lines 6076 6207 +131
===========================================
+ Hits 6076 6161 +85
- Misses 0 46 +46 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
I think we decided not to do this. We have some better support with https://jump.dev/JuMP.jl/dev/tutorials/getting_started/debugging/#Debugging-performance-problems |
|
I am not sure we should close yet. |
|
I don't know what the right approach is, but after thinking about this more I don't think that it's this PR. |
This adds the optional ability to mark all places where slow operations that allocate expression occur. Keeping the stack might be a lot of data, but it is a way to properly identify the issues instead of erroring one by one.
Possible additional functionality:
1 - also mark the operation type. A bit redundant with the stack, but might lead to summary reports.
2 - create a user friendly summary
TODO