Add some more code modification hints

git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@68261 91177308-0d34-0410-b5e6-96231b3b80d8

1 files changed, 6 insertions, 2 deletions

diff --git a/TODO.txt b/TODO.txt
index df65be409d..522dcd37b3 100644
--- a/TODO.txt
+++ b/TODO.txt
@@ -60,5 +60,9 @@ page full of results (say, 50 lines of text). Beyond that, (1) the
 remaining errors are likely to be less interesting, and (2) the poor
 user has to scroll his terminal to find out where things went wrong.
 
-
-
+//===---------------------------------------------------------------------===//
+More ideas for code modification hints:
+  - If no member of a given name is found in a class/struct, search through the names of entities that do exist in the class and suggest the closest candidate. e.g., if I write "DS.setTypeSpecType", it would suggest "DS.SetTypeSpecType" (edit distance = 1).
+  - If a class member is defined out-of-line but isn't in the class declaration (and there are no close matches!), provide the option to add an in-class declaration.
+  - Fix-it hints for the inclusion of headers when needed for particular features (e.g., <typeinfo> for typeid)
+  - Change "foo.bar" to "foo->bar" when "foo" is a pointer.