fix: handle attempts to merge function into block coverage

[bcoe]

The Node.js test suite runs into situations where attempts are made to merge function granularity coverage into block level granularity, leading to incorrect coverage reports:

this issue can be addressed by always preferring block level coverage.

fixes: #2

[demurgos]

Sorry for the long delay: I missed the notification. I'll take a look at the PR and merge it.

[bcoe]

@demurgos the other issue I bumped into yesterday trying to use this at work was that /gs on regexes was having trouble on Windows, because you're splitting lines on \n, I think we can just drop the s and make the regexes in ascii.js, /g.

[demurgos]

Thank you for the PR: I looked into the issue and your solution. I agree that the current implementation is clearly wrong in its handling of mixed block and non-block function coverages.

There's a bit of information lost here (block level coverage overrides non-block level) but this PR is simple and improves the current situation so I'll merge it and publish it to npm. I'll keep the issue open for the the moment though: I'd like to see if there's a way to keep both block coverage and non-block coverage information that is suitable for consumers.

[demurgos]

Regarding ascii.js, I expected this file to be system-agnostic and help generate fixtures from ascii diagrams. I'll send a follow-up PR to fix it.