Michael Förderer
Michael Förderer
Do you've an idea why there are different calls generated for the same template instantiation? The extra block ID `2` is also the source of the extra call: ```yaml {...
E.g. if we get two branches from one report and four from another we will have at the end six branches over all. The line coverage won't be affected.
@dlegaultbbry, @Pesa I've improved the merging of elements. Same elements are detected by the numbers, which are preserved in the JSON output, and the block information.
@Pesa The warnings are removed because we now merge the branches by comparing the properties.
I'll merge this now because I found a bug in the text parser with function specialisations and in the writers using the line coverage if there are specialisations. Th fix...
The horizontal lines is used between conditions from different line coverage entries for the same line. If there is no horizontal line we've only a list of conditions. If there...
@Pesa Here I build an example with a template function which is instantiated twice. There are three possibilities: | Number of condition blocks | Conditions in block | Prefix in...
@Pesa Is it better this way? 
I'll raise a PR for this but first I wan't to fix the merging of coverage data where we get different results from GCOV.
Details view was improved but link was missing.