[llvm-bugs] [Bug 33381] New: No completions after known identifier / function call

via llvm-bugs llvm-bugs at lists.llvm.org
Fri Jun 9 00:12:37 PDT 2017


https://bugs.llvm.org/show_bug.cgi?id=33381

            Bug ID: 33381
           Summary: No completions after known identifier / function call
           Product: clang
           Version: trunk
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: libclang
          Assignee: unassignedclangbugs at nondot.org
          Reporter: nikolai.kosjar at qt.io
                CC: klimek at google.com, llvm-bugs at lists.llvm.org

Consider this:

$ cat -n $FILE                                      
     1  void f()
     2  {
     3      bla  // Complete just before '/'
     4  }
$ ./c-index-test -code-completion-at=$FILE:3:9 $FILE 
<many may completion items>

That's fine and expected. Now let's declare "bla" before this and re-check:

$ cat -n $FILE                                       
     1  void f(int bla)
     2  {
     3      bla  // Complete just before '/'
     4  }
$ ./c-index-test -code-completion-at=$FILE:3:9 $FILE 
Completion contexts:
Unknown
Any type
Any value
Objective-C object value
Objective-C selector value
C++ class type value
Dot member access
Arrow member access
Objective-C property access
Enum tag
Union tag
Struct tag
Class name
Namespace or namespace alias
Nested name specifier
Objective-C interface
Objective-C protocol
Objective-C category
Objective-C instance method
Objective-C class method
Objective-C selector name
Macro name
Natural language
$

Ops, no completion items at all are provided.

Same happens if "bar" is declared as a function and you try to complete
directly after the function call (no semicolon).

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20170609/b9c9ec69/attachment-0001.html>


More information about the llvm-bugs mailing list