btw, if anyone else is interested in collaborating...
# code-coverage
p
btw, if anyone else is interested in collaborating on a solution to this problem, either DM me or start a thread.
I was thinking that an interim solution could be hacked out by leveraging compiler provided data, like -Xprint-locations provides, which the native compiler uses for debug information. This might be possible but looks to be a ton of work.
It now occurs to me that if the IntelliJ code coverage code could be wrapped into a Gradle plugin, that would be quite nice for manual and CI tool use.