1 //===---------------------------------------------------------------------===//
2 // Minor random things that can be improved
3 //===---------------------------------------------------------------------===//
6 Warn about "X && 0x1000" saying that the user may mean "X & 0x1000".
7 We should do this for any immediate except zero, so long as it doesn't come
8 from a macro expansion. Likewise for ||.
10 //===---------------------------------------------------------------------===//
12 Lexer-related diagnostics should point to the problematic character, not the
13 start of the token. For example:
18 diag.c:4:9: error: invalid digit '8' in octal constant
24 diag.c:4:9: error: invalid digit '8' in octal constant
28 This specific diagnostic is implemented, but others should be updated.
30 //===---------------------------------------------------------------------===//
32 C++ (checker): For iterators, warn of the use of "iterator++" instead
33 of "++iterator" when when the value returned by operator++(int) is
36 //===---------------------------------------------------------------------===//
38 We want to keep more source range information in Declarator to help
39 produce better diagnostics. Declarator::getSourceRange() should be
40 implemented to give a range for the whole declarator with all of its
41 specifiers, and DeclaratorChunk::ParamInfo should also have a source
42 range covering the whole parameter, so that an error message like this:
44 overloaded-operator-decl.cpp:37:23: error: parameter of overloaded post-increment operator must have type 'int' (not 'float')
45 X operator++(X&, const float& f);
47 can be turned into something like this:
49 overloaded-operator-decl.cpp:37:23: error: parameter of overloaded post-increment operator must have type 'int' (not 'float')
50 X operator++(X&, const float& f);
53 //===---------------------------------------------------------------------===//
55 For terminal output, we should consider limiting the amount of
56 diagnostic text we print once the first error has been
57 encountered. For example, once we have produced an error diagnostic,
58 we should only continue producing diagnostics until we have produced a
59 page full of results (say, 50 lines of text). Beyond that, (1) the
60 remaining errors are likely to be less interesting, and (2) the poor
61 user has to scroll his terminal to find out where things went wrong.