5cec2aea3f
Previously we would cut off the source file buffer at the code-completion point; this impeded code-completion inside C++ inline methods and, recently, with buffering ObjC methods. Have the code-completion inserted into the source buffer so that it can be buffered along with a method body. When we actually hit the code-completion point the cut-off lexing or parsing. Fixes rdar://10056932&8319466 llvm-svn: 139086
25 lines
804 B
C++
25 lines
804 B
C++
class MyCls {
|
|
void in_foo() {
|
|
vec.x = 0;
|
|
}
|
|
void out_foo();
|
|
|
|
struct Vec { int x, y; };
|
|
Vec vec;
|
|
};
|
|
|
|
void MyCls::out_foo() {
|
|
vec.x = 0;
|
|
}
|
|
|
|
// RUN: c-index-test -code-completion-at=%s:3:9 %s | FileCheck %s
|
|
// RUN: c-index-test -code-completion-at=%s:12:7 %s | FileCheck %s
|
|
// CHECK: CXXMethod:{ResultType MyCls::Vec &}{TypedText operator=}{LeftParen (}{Placeholder const MyCls::Vec &}{RightParen )} (34)
|
|
// CHECK-NEXT: StructDecl:{TypedText Vec}{Text ::} (75)
|
|
// CHECK-NEXT: FieldDecl:{ResultType int}{TypedText x} (35)
|
|
// CHECK-NEXT: FieldDecl:{ResultType int}{TypedText y} (35)
|
|
// CHECK-NEXT: CXXDestructor:{ResultType void}{TypedText ~Vec}{LeftParen (}{RightParen )} (34)
|
|
// CHECK-NEXT: Completion contexts:
|
|
// CHECK-NEXT: Dot member access
|
|
// CHECK-NEXT: Container Kind: StructDecl
|