Why generate MCDC conditions for constant flows?
__test1_PP_1 = (true -> false);
_cov_12_16 = __test1_PP_1;
__cov_13_16 = (not (_test1_PP_1));
_cov_14_16 = __test1_PP_1;
__cov_15_16 = (not (_test1_PP_1));
I am not sure it is a bug:
- either it is a pure constant like b = true
then a condition if b then e1 else e2 will produce the two conditions and we may discover that e2 is dead code
- or it is a non constant constant :) true -> false changes over time. Then it makes sense to evaluate both cases.