Oliver Stöneberg

I think all three are valid. Example 1 is not about saving code but redundancies. The type is clearly specified so there is no need to specify it again. So that should be done. Example 2 it would help understanding the code but if you are using a proper IDE the tooltip should take care of that. Example 3 it saves a lot of space and I think this is about the as_const() as well. I think that is a good use of auto and again the IDE tooltip would be good here. Buit in case of 2 or 3 I could go either...

Also note that this is detected by Clang: <source>:4:1: warning: all paths through this function will call itself [-Winfinite-recursion] 4 | { | ^

What issue do you expect to see? From a quick look it seems this will produce an infinite recursion but that is nothing which was ever reported by Cppcheck.

Thanks for your report. I filed https://trac.cppcheck.net/ticket/14539 about it.

Yes, that is a known shortcoming. When you use a binary compiled on a Linux system (even WSL) we assume that all files are case sensitive. But that is not dependent on the system but the underlying filesystem. These issues are already tracked in the underlying simplecpp library via https://github.com/danmar/simplecpp/issues/308 and https://github.com/danmar/simplecpp/issues/309.

Yesm that is a known shortcoming. When you use a binary compiled on a Linux system (even WSL) we assume that all files are case sensitive. But that is not dependent on the system but the underlying filesystem. These issues are already tracked in the underlying simplecpp library via https://github.com/danmar/simplecpp/issues/308 and https://github.com/danmar/simplecpp/issues/309.

Thanks for your report. --include-file does not exist so I assume you meant --include=<file>. I filed https://trac.cppcheck.net/ticket/14538 about this.

Thanks for your report. I filed https://trac.cppcheck.net/ticket/14537 about supporting this.