chrchr-github
chrchr-github
This seems to work after adjusting one test case: ~~~ namespace { const Function* getFunctionForArgumentvariable(const Variable * const var, const std::vector& functionScopes) { const std::size_t functions = functionScopes.size(); for (std::size_t...
See https://github.com/danmar/cppcheck/pull/6118 I think the impact on performance should be negligible (linear in the number of variables).
> `i a;u n(;a[]),n(){a[]=0}` `(;` should be a `syntaxError`
Feel free to reopen once comments have been addressed.
With your fix applied, we produce invalid code like `namespace N { enum E { } ; } void g ( int ) ; void f ( ) { g...
Seems like the remaining bailouts are cfg-related, except for that uninstantiated(?) template parameter.
> ``` > gui/codeeditorstyle.cpp:125:40: debug: valueflow.cpp:10106:valueFlowConditionExpressions bailout: Skipping function due to incomplete variable widgetFGColor [valueFlowBailoutIncompleteVar] > QVariant(defaultStyleLight.widgetFGColor)).value(); > ^ > ``` https://trac.cppcheck.net/ticket/10045#comment:30
Thanks for your contribution. Please add a test for your fix. I expect that some logic must be added to pass the existing tests, see also the history of ticket...
Feel free to reopen after CI issues are fixed.
Not sure where it is used, but `isEnumStart()` doesn't seem to handle e.g. `enum E : ::std::uint8_t {`. I also dimly remember adding a similar function recently somewhere.