You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@samuelroy
In light of things like #13, I think we can do much better and 100% accuracy (maybe) by using compiler support (via instrumentation of the nim code directly) instead of lcov based approach.
Let me know if you'd be interested in exploring that approach, happy to help; I think it's very doable.
Code coverage is a very useful basic feature that helps with many things, eg testing, finding bugs, improving code quality in general, so it's an important feature nim should have
implementation details
I think looking at optProfiler in nim code (enabled by nim --profiler:on) should be a good starting point
I've already looked at implementing my own profiler based on how nimprof works with no success so far.
The profiler seems to work only in a sampling mode. Do you have a working example of code instrumentation with Nim?
@samuelroy
In light of things like #13, I think we can do much better and 100% accuracy (maybe) by using compiler support (via instrumentation of the nim code directly) instead of lcov based approach.
Let me know if you'd be interested in exploring that approach, happy to help; I think it's very doable.
Code coverage is a very useful basic feature that helps with many things, eg testing, finding bugs, improving code quality in general, so it's an important feature nim should have
implementation details
I think looking at
optProfiler
in nim code (enabled bynim --profiler:on
) should be a good starting pointEDIT
see https://forum.nim-lang.org/t/7024#44128 where I detail what I've worked on (tracing)
The text was updated successfully, but these errors were encountered: