Closed killy971 closed 10 years ago
As part of the mix entries generated by hpc for an otherwise
expression used as a guard, there should be one of the following type, which Tix value will be 0
:
(6:22-6:30,BinBox GuardBinBox False)
The tix value for this entry should therefore be treated as a 1
.
Feature branch: consider-otherwise-covered
Fixed by 3072f1753f59ad5e0bd6fde2172906bb781b33f5
HPC flags
otherwise
as always True, which may be correct, but is not really interesting in terms of code coverage.If possible, hpc-coveralls could be improved to consider the
otherwise
expression to be always fully covered, as well as other similar patterns.