flovent
flovent
> but won't this fail with a std::map, since the key is an integer? It won't, `ArraySubScriptExpr` is generated here because variable `map`'s type is dependent, it's AST: ``` ArraySubscriptExpr...
@vbvictor, thanks for the review! I just rebased and merged test case to this check's original test file.
> Thanks for the detailed PR summary. It makes sense. I had to think about it carefully but I agree with the motivation. When I looked at the code it...
CI failures seem unlreated to the new change in this PR.
> Also please follow the [Coding Standard](https://llvm.org/docs/CodingStandards.html#name-types-functions-variables-and-enumerators-properly) and use `UpperCamelCase` variables for variables (including ones that store lambda functions), while `lowerCamelCase` is for methods. Of course, it is also right...
Oh, sorry about that. It seems an error node will be generated when emitting `alpha.unix.cstring.OutOfBounds` warning, so rest of code will not be analyzed.
@NagyDonat, I add a note in the end of PR description and I don't have a merge access, if that looks good please help me merge it, thank you!
Maybe vscode don't support this indeed, i tried `go` and `python` extension, the output of type hierarchy and call hierarchy has the same behaviour as vscode-clangd. I'll see if i...
> Maybe vscode don't support this indeed, i tried go and python extension, the output of type hierarchy and call hierarchy has the same behaviour as vscode-clangd. I tried to...