Lukas Atkinson

What you're trying to do has not been tested yet, so I'd be interested to hear back about the results. But I think you can only merge JSON reports if...

yes, something like a `--json-base` option sounds pretty sensible. I don't want to reuse the `--root` value because it already has multiple roles.

That's a great idea! But it is a bit tricky: * [The branches are real](https://gcovr.com/en/master/faq.html#why-does-c-code-have-so-many-uncovered-branches) so it does make sense to show them. * But these branches are not generally...

Currently, gcovr does not support function coverage. In the meanwhile, you would have to use lcov for coverage reports, which does support this. The underlying data from GCC/gcov does include...

Thanks! If you'd like to try doing this, look at the [contribution guidelines](https://gcovr.com/en/master/contributing.html) for how to set up a development environment etc. A couple of pointers: * we'd have to...

@decimad GCC/gcov does know where functions start and end. However, the human-readable .gcov format that we parse does not include this information. At most, we could count lines towards the...

@Toolazy2cruel It seems you have implemented a parser for function coverage? If you could open a pull request with that code, I'd love to merge it into gcovr. Once function...

I have yet to see an example .gcov file that exhibits the issue, but I'm 95% certain this is a problem in gcov. Gcovr is written in Python which features...

Thank you for this excellent report. The present source file has a curios pattern that has different definitions for a function depending on preprocessor `#define`s. Basically: ```c++ #if ALLPIX_MODULE_UNIQUE Module*...

Ok, I'll think about a way to skip this check on an opt-in basis, for example with a new `--allow-duplicate-functions` flag. I'd really like to keep an assertion because it...