| 651f13cea278ec967336033dd032faef0e9fc2ec |
|
24-Apr-2014 |
Stephen Hines <srhines@google.com> |
Updated to Clang 3.5a.
Change-Id: I8127eb568f674c2e72635b639a3295381fe8af82
/external/clang/test/Index/complete-recovery.m
|
| 436bd50a3821c0f7a859af0e423d5c0a55159bf1 |
|
01-Dec-2011 |
Lang Hames <lhames@gmail.com> |
Test case for fix committed in r145441.
git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@145534 91177308-0d34-0410-b5e6-96231b3b80d8
/external/clang/test/Index/complete-recovery.m
|
| 8ca7208d0fb4dcbc5fa8cfeca6a1081ce69da8e0 |
|
18-Oct-2011 |
Douglas Gregor <dgregor@apple.com> |
Provide result types for code completions that describe built-in
expressions (this, sizeof, etc.).
git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@142424 91177308-0d34-0410-b5e6-96231b3b80d8
/external/clang/test/Index/complete-recovery.m
|
| 7d100872341f233c81e1d7b72b40457e62c36862 |
|
04-Sep-2011 |
Argyrios Kyrtzidis <akyrtzi@gmail.com> |
Support code-completion for C++ inline methods and ObjC buffering methods.
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
git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@139086 91177308-0d34-0410-b5e6-96231b3b80d8
/external/clang/test/Index/complete-recovery.m
|
| 140ab234c23f392d5422691c5de1ee3c15026def |
|
31-Aug-2011 |
Fariborz Jahanian <fjahanian@apple.com> |
objective-c - This patch buffers method implementations
and does the Sema on their body after the entire
class/category @implementation is seen. This change allows messaging
of forward private methods, as well as, access to
synthesized ivars of properties with foward synthesize
declarations; among others. In effect, this patch removes
several restrictions placed on objective-c due to in-place
semantics processing of methods.
This is part of // rdar://8843851.
git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@138865 91177308-0d34-0410-b5e6-96231b3b80d8
/external/clang/test/Index/complete-recovery.m
|
| 8ec904c151abf7ed0dc911258574a904ed97ff15 |
|
19-Oct-2010 |
Douglas Gregor <dgregor@apple.com> |
Tweak code-completion result priorities, so that exact and similar
type matches have a bigger impact. The impetus for this change was
that, when initializing an enumeration value, we want enumerators of
that enumeration type to have a higher priority than, e.g., unrelated
local variables.
git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@116774 91177308-0d34-0410-b5e6-96231b3b80d8
/external/clang/test/Index/complete-recovery.m
|
| 32be4a588fbb87d0d163ead49c42f5438bf0b2b7 |
|
11-Oct-2010 |
Douglas Gregor <dgregor@apple.com> |
Switch c-index-test from clang_codeComplete() over to
clang_codeCompleteAt(). This uncovered a few issues with the latter:
- ASTUnit wasn't saving/restoring diagnostic state appropriately between
reparses and code completions.
- "Overload" completions weren't being passed through to the client
git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@116241 91177308-0d34-0410-b5e6-96231b3b80d8
/external/clang/test/Index/complete-recovery.m
|
| 833ba9c6913d825016b432b0c4e4f784b1a9eb87 |
|
18-Sep-2010 |
Douglas Gregor <dgregor@apple.com> |
Add another text for code completion after recovery
git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@114257 91177308-0d34-0410-b5e6-96231b3b80d8
/external/clang/test/Index/complete-recovery.m
|
| ac5fd8404fa8ecfae28be76f98fd0d926350354c |
|
18-Sep-2010 |
Douglas Gregor <dgregor@apple.com> |
Continue parsing more postfix expressions, even after semantic
errors. Improves code completion in yet another case.
git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@114255 91177308-0d34-0410-b5e6-96231b3b80d8
/external/clang/test/Index/complete-recovery.m
|
| 94859890384652ed63f7604530f3b988ed223cf4 |
|
18-Sep-2010 |
Douglas Gregor <dgregor@apple.com> |
Improve recovery when the middle expression of a ternary operator is ill-formed
git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@114231 91177308-0d34-0410-b5e6-96231b3b80d8
/external/clang/test/Index/complete-recovery.m
|
| 200b2921390bd75a659be3c77011e9a5548b7273 |
|
18-Sep-2010 |
Douglas Gregor <dgregor@apple.com> |
When we run into an error parsing or type-checking the left-hand side
of a binary expression, continue on and parse the right-hand side of
the binary expression anyway, but don't call the semantic actions to
type-check. Previously, we would see the error and then, effectively,
skip tokens until the end of the statement.
The result should be more useful recovery, both in the normal case
(we'll actually see errors beyond the first one in a statement), but
it also helps code completion do a much better job, because we do
"real" code completion on the right-hand side of an invalid binary
expression rather than completing with the recovery completion. For
example, given
x = p->y
if there is no variable named "x", we can still complete after the p->
as a member expression. Along the recovery path, we would have
completed after the "->" as if we were in an expression context, which
is mostly useless.
git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@114225 91177308-0d34-0410-b5e6-96231b3b80d8
/external/clang/test/Index/complete-recovery.m
|
| 9536572c72d6076f4dc741615195dd5bdc04d287 |
|
03-Sep-2010 |
Daniel Dunbar <daniel@zuster.org> |
Avoid unnecessary redirect, so that stderr shows up in output.
git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@112965 91177308-0d34-0410-b5e6-96231b3b80d8
/external/clang/test/Index/complete-recovery.m
|
| 4710e5b12b58dda87d82c5875f13ab9c8979cd8c |
|
28-May-2010 |
Douglas Gregor <dgregor@apple.com> |
Do not produce types as valid code completions when we're in an
expression context in C/Objective-C, or when we're in an
@interface/@implementation/@protocol in Objective-C(++).
git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@104908 91177308-0d34-0410-b5e6-96231b3b80d8
/external/clang/test/Index/complete-recovery.m
|
| d8e8a58ee35ab334ab9d0c2154dca029c1822e8a |
|
25-May-2010 |
Douglas Gregor <dgregor@apple.com> |
Only enable code patterns (e.g., try { statements } catch (...) {
statements }) in the code-completion results if explicitly requested.
git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@104637 91177308-0d34-0410-b5e6-96231b3b80d8
/external/clang/test/Index/complete-recovery.m
|
| dc8453422bec3bbf70c03920e01498d75783d122 |
|
25-May-2010 |
Douglas Gregor <dgregor@apple.com> |
Improve code completion in failure cases in two ways:
1) Suppress diagnostics as soon as we form the code-completion
token, so we don't get any error/warning spew from the early
end-of-file.
2) If we consume a code-completion token when we weren't expecting
one, go into a code-completion recovery path that produces the best
results it can based on the context that the parser is in.
git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@104585 91177308-0d34-0410-b5e6-96231b3b80d8
/external/clang/test/Index/complete-recovery.m
|