- when a method is not available because of the target value kind (e.g. an && method on a Foo& variable), then don't offer it.
- when a method is effectively shadowed by another method from the same class with a) an identical argument list and b) superior qualifiers, then don't offer it.
Details
Diff Detail
- Repository
- rC Clang
- Build Status
Buildable 32735 Build 32734: arc lint + arc unit
Event Timeline
lib/Sema/SemaCodeComplete.cpp | ||
---|---|---|
1308 | Won't this crash on Method->getName()? Could we add a test for that? | |
1316 | Could you add a comment that we modify previously added results here? |
Handle methods without "normal" identifier names.
Add comments.
Trigger in both directions (dominated and dominated-by).
Oops, we weren't handling the case when the newly-added overload is dominated by an existing one. Fixed.
lib/Sema/SemaCodeComplete.cpp | ||
---|---|---|
1308 | Right! Fixed and test added. We now no longer hash the strings which is nice too. |
LGTM
lib/Sema/SemaCodeComplete.cpp | ||
---|---|---|
1314 | A leftover debug output. Please remove before landing |
Won't this crash on Method->getName()? Could we add a test for that?
Completing in a class that has a user-defined operator==() would probably do the trick.