[IDEA] Convert types to correct ones: `for(int i=0; i<vec.size(); i++)` => `for(size_t i=0; i<vec.size(); i++)` about clang-tutor HOT 6 OPEN

Thanks, good idea, I've made a repo and will see how far I can get once the boilerplate is done: https://github.com/SamuelMarks/type-correct

(can use that same boilerplate for the #22 repo… I'm not a fan of monorepos 📦)

from clang-tutor.

Hey,

This would be incredibly useful, yes! Which makes me wonder - has there been any prior art? Have you tried UndefinedBehaviorSanitizer?

With this sort of tools, you want to make sure that you don't get too many false positives. Preferably none. That's the tricky part. Also, I guess that you'd want to identify the problematic cases first and then refactor them, right? As in, a proof-of-concept for this could be implemented in two steps.

Are you aware of a good code-base that could be used to showcase this?

I'm more than happy to help. I don't do much in Clang myself, so I'm not an expert. But I am always keen to learn something new! I've noticed that you have already asked on Discourse. From my experience, Clang folk mostly use cfe-dev. You could try there if there are no replies on Discourse.

All the best,
Andrzej

from clang-tutor.

Thanks Andrzej,

Yeah there are a bunch of nice santisers out there… but I haven't found any that improve the code for you in this way.

I assume there are two trivial cases which should be comparatively straightforward to implement:

0. Convert type of variable to return type of function (function type takes precedence)… à la auto in C++11;
1. Convert loop initialiser var—and C89 style var initialised in var but declared elsewhere—that is compared with a var of another type, to the comparison var type (first non-equal var type being compared against takes precedence).

Not sure if I try to hack something together now—with you to check—or if I continue the RFC onto cfe-dev. Oh and also the IRC channel was helpful (if you get there at the right time-of-day).

from clang-tutor.

So you probably want to start with something simple like this:

void foo() {
  unsigned K = 10;
  for (int k = 0; k < K; k++)
    ;
}

Try this:

$ clang -Wextra -c file.cpp
file.cpp:3:22: warning: comparison of integers of different signs: 'int' and 'unsigned int' [-Wsign-compare]
  for ( int k = 0; k < K; k++)
                   ~ ^ ~

So it is possible to analyse this with clang and identify as a problem. Now,

$ clang -cc1 -ast-dump -fcolor-diagnostics file.cpp
TranslationUnitDecl 0x745dae8 <<invalid sloc>> <invalid sloc>
|-TypedefDecl 0x745e410 <<invalid sloc>> <invalid sloc> implicit __int128_t '__int128'
| `-BuiltinType 0x745e0b0 '__int128'
|-TypedefDecl 0x745e480 <<invalid sloc>> <invalid sloc> implicit __uint128_t 'unsigned __int128'
| `-BuiltinType 0x745e0d0 'unsigned __int128'
|-TypedefDecl 0x745e7f8 <<invalid sloc>> <invalid sloc> implicit __NSConstantString '__NSConstantString_tag'
| `-RecordType 0x745e570 '__NSConstantString_tag'
|   `-CXXRecord 0x745e4d8 '__NSConstantString_tag'
|-TypedefDecl 0x745e890 <<invalid sloc>> <invalid sloc> implicit __builtin_ms_va_list 'char *'
| `-PointerType 0x745e850 'char *'
|   `-BuiltinType 0x745db90 'char'
|-TypedefDecl 0x74a3268 <<invalid sloc>> <invalid sloc> implicit __builtin_va_list '__va_list_tag [1]'
| `-ConstantArrayType 0x74a3210 '__va_list_tag [1]' 1
|   `-RecordType 0x745e980 '__va_list_tag'
|     `-CXXRecord 0x745e8e8 '__va_list_tag'
`-FunctionDecl 0x74a3308 <file.cpp:1:1, line:5:1> line:1:6 foo 'void ()'
  `-CompoundStmt 0x74a3698 <col:12, line:5:1>
    |-DeclStmt 0x74a34a8 <line:2:3, col:18>
    | `-VarDecl 0x74a3408 <col:3, col:16> col:12 used K 'unsigned int' cinit
    |   `-ImplicitCastExpr 0x74a3490 <col:16> 'unsigned int' <IntegralCast>
    |     `-IntegerLiteral 0x74a3470 <col:16> 'int' 10
    `-ForStmt 0x74a3660 <line:3:3, line:4:5>
      |-DeclStmt 0x74a3560 <line:3:9, col:18>
      | `-VarDecl 0x74a34d8 <col:9, col:17> col:13 used k 'int' cinit
      |   `-IntegerLiteral 0x74a3540 <col:17> 'int' 0
      |-<<<NULL>>>
      |-BinaryOperator 0x74a3600 <col:20, col:24> 'bool' '<'
      | |-ImplicitCastExpr 0x74a35e8 <col:20> 'unsigned int' <IntegralCast>
      | | `-ImplicitCastExpr 0x74a35b8 <col:20> 'int' <LValueToRValue>
      | |   `-DeclRefExpr 0x74a3578 <col:20> 'int' lvalue Var 0x74a34d8 'k' 'int'
      | `-ImplicitCastExpr 0x74a35d0 <col:24> 'unsigned int' <LValueToRValue>
      |   `-DeclRefExpr 0x74a3598 <col:24> 'unsigned int' lvalue Var 0x74a3408 'K' 'unsigned int'
      |-UnaryOperator 0x74a3640 <col:27, col:28> 'int' postfix '++'
      | `-DeclRefExpr 0x74a3620 <col:27> 'int' lvalue Var 0x74a34d8 'k' 'int'
      `-NullStmt 0x74a3658 <line:4:5>

Clearly there's enough context there for this simple case.

You are more than welcome to start hacking here. But you might get more feedback from more experienced Clang developers on cfe-dev. And if people find this feasible and useful, it might be better to contribute this directly to Clang. Again - this could attract some quality reviews. And I'm active on Phabricator too.

from clang-tutor.

@banach-space Trying to be as succinct as possible, with my directory layout, lines of code, and everything. There's a lot of boilerplate to remember / reverse-engineer from your repo!

WiP (contributions welcome)

from clang-tutor.

There's https://github.com/banach-space/clang-tutor/tree/main/HelloWorld as a minimal example. But otherwise, yeah, takes a bit of time to set everything up.

from clang-tutor.