András Dóczi

I think having the plugin name on the right side of the option name-value pair is counter-intuitive. Normally `--foo bar` means "set *foo* to *bar*", which means `-i cppparser:compile_commands.json` reads...

I would argue that moving some of the configuration to config files would actually *increase* the complexity of using the CLI. Most of these arguments will likely change from project...

Storing the config does sound like a good idea. What I meant was having to prepare a config file when setting up a *new* project with advanced args (this is...

It was mentioned in the last meeting that putting all the plugin-specific flags in the same "namespace" is a bad idea -- this can lead to name collisions if two...

I realized this happens because template specializations are considered separate entities. So technically what we're seeing is correct, but I don't think it's a very good UI. It would be...

Wouldn't it be enough to aggregate references? For example, if `myfunc()` calls `a()` and `myfunc()` calls `b1()` and `b2()`, then querying the callees of `myfunc()` would return `[a(), b1(), b2()]`.

I checked Understand, Woboq and Visual Studio 2019, and they completely ignore template specializations. When listing usages/callers/callees, they treat template functions and classes as if the part between `` wasn't...

CodeChecker's logger keeps the include paths as-is, it never converts a relative path to an absolute one or vice-versa. I think the proper fix would be to make the C++...

It turns out there's a bug I didn't catch: if the build directory doesn't exist, the parsing fails, because `RealFileSystem` requires that the `chdir` target exists. To fix this, I'll...

> How is it possible to have a build generated with CMake (which creates directory structures) or logged (in which case the build was executed and should have created the...