Michael Förderer
Michael Förderer
You can start on this.
Good question. I would go in direction one with following properties: - `total`: Overall number of items. - `excluded`: Number of excluded items. - `covered`: Number of covered items. This...
This wasn't a question. This was a con for approach 2. We need to think also if we need the option `--excluded-stats` at all or if we shall always add...
I was only thinking about the lines and branches excluded by comments. If we do this for all exclusion possibilities this would be quite complicated for the file exclusions. If...
> Most reports would still only focus on the covered:reportable ratio. On a per-file level, statistics about "excluded via marker pattern" may be meaningful, perhaps this can be surfaced in...
@dlegaultbbry Can you start with the changes to the data model as described in https://github.com/gcovr/gcovr/issues/988#issuecomment-2480737446?
Yes, please update the JSON version and the documentation.
No problem, it's your own request. 😄
What do you think about also extending our comment syntax with an option to add a justification for the exclusion? In that case we need to create a metric with...
Sorry for my late response. I was thinking about something like: ```C // GCOVR_EXCL_START | : // GCOVR_EXCL_START | EFFORT: Writing a test for this isn't worth the effort //...