| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| |
|
|
|
|
| |
declarations we're adding do not need any name-hiding checks.
llvm-svn: 93431
|
| |
|
|
|
|
| |
eliminating yet one more ResultBuilder::MaybeAddResult caller.
llvm-svn: 93430
|
| |
|
|
|
|
| |
ResultBuilder::MaybeAddResult over to ResultBuilder::AddResult.
llvm-svn: 93429
|
| |
|
|
|
|
|
|
| |
after adding the ability to determine whether our lookup is a
base-class lookup. Eliminate CollectMemberLookupResults, since it is
no longer used (yay).
llvm-svn: 93428
|
| |
|
|
|
|
| |
broken way that can give conflicts on method names containing underscores, but is needed for gdb to work because gdb does not know how to read ObjC class tables and relies on the mangling).
llvm-svn: 93427
|
| |
|
|
| |
llvm-svn: 93422
|
| |
|
|
|
|
| |
LookupVisibleDecls. Also, a function does not hide another function.
llvm-svn: 93421
|
| |
|
|
|
|
|
| |
for special diagnostics. Unfortunately, the non-overload diagnostics are not
this good.
llvm-svn: 93420
|
| |
|
|
|
|
| |
of the more general LookupVisibleDecls.
llvm-svn: 93419
|
| |
|
|
|
|
|
| |
than traversing visible declarations twice, only perform one traversal
and recognize nested-name-specifiers as special.
llvm-svn: 93418
|
| |
|
|
|
|
| |
Thanks Ted.
llvm-svn: 93413
|
| |
|
|
|
|
| |
builder, because that's the only time they're needed.
llvm-svn: 93412
|
| |
|
|
|
|
|
|
| |
need an error term for the CFG. I suspect we'll always have to cope
with getCFG returning 0, though, I'd love to see even that possibility
removed.
llvm-svn: 93411
|
| |
|
|
| |
llvm-svn: 93405
|
| |
|
|
|
|
| |
namespaces and functions.
llvm-svn: 93404
|
| |
|
|
| |
llvm-svn: 93399
|
| |
|
|
|
|
|
| |
provided nested-name-specifier results for base classes (only), rather
than everything that could possibly be a nested-name-specifier.
llvm-svn: 93398
|
| |
|
|
|
|
|
|
|
|
| |
LookupVisibleDecls, unifying the name lookup mechanisms used by code
completion and typo correction. Aside from the software-engineering
improvements, this makes code-completion see through using directives
and see ivars when performing unqualified name lookup in an
Objective-C instance method.
llvm-svn: 93397
|
| |
|
|
|
|
| |
about 'object argument' vs. 'nth argument'.
llvm-svn: 93395
|
| |
|
|
|
|
|
| |
English right now; would not be impossible to grab a special format string
from the diagnostic pool and localize that way.
llvm-svn: 93390
|
| |
|
|
|
|
| |
concerned. It is expected that this is set (usually left bracket location of function body compound statement) before EmitfunctionStart() is used.
llvm-svn: 93389
|
| |
|
|
|
|
| |
functionality change.
llvm-svn: 93386
|
| |
|
|
|
|
| |
if it matches regular name.
llvm-svn: 93383
|
| |
|
|
|
|
|
|
| |
place.
Fixes radar 7284618.
llvm-svn: 93382
|
| |
|
|
|
|
| |
code-completion's ResultBuilder::MaybeAddResult for later reuse.
llvm-svn: 93379
|
| |
|
|
| |
llvm-svn: 93378
|
| |
|
|
| |
llvm-svn: 93377
|
| |
|
|
|
|
| |
are no longer using it for anything. No intended functionality change.
llvm-svn: 93376
|
| |
|
|
|
|
|
|
| |
the "typed" text, first, then take into account
nested-name-specifiers, name hiding, etc. This means that the
resulting sort is actually alphabetical :)
llvm-svn: 93370
|
| |
|
|
|
|
|
|
|
|
|
|
| |
to be considering user-defined conversions in the first place.
Doug, please review; I'm not sure what we should be doing if we see a real
ambiguity in selecting a copy constructor when otherwise suppressing
user-defined conversions.
Fixes PR6014.
llvm-svn: 93365
|
| |
|
|
| |
llvm-svn: 93362
|
| |
|
|
| |
llvm-svn: 93361
|
| |
|
|
|
|
| |
function 'MakeCXCursor' to centralize the logic for creating CXCursor objects.
llvm-svn: 93359
|
| |
|
|
|
|
| |
constructor. Fixes radar 7537770.
llvm-svn: 93358
|
| |
|
|
|
|
|
|
|
|
|
| |
provide completions for @ keywords. Previously, we only provided
@-completions after an @ was actually typed, which is useful but
probably not the common case.
Also, make sure a few Objective-C 2.0 completions only show up when
Objective-C 2.0 support is enabled (the default).
llvm-svn: 93354
|
| |
|
|
| |
llvm-svn: 93353
|
| |
|
|
| |
llvm-svn: 93348
|
| |
|
|
| |
llvm-svn: 93347
|
| |
|
|
| |
llvm-svn: 93346
|
| |
|
|
|
|
| |
yet used.
llvm-svn: 93345
|
| |
|
|
|
|
| |
Patch by Enea Zaffanella.
llvm-svn: 93344
|
| |
|
|
|
|
| |
declaration references from other delcarations.
llvm-svn: 93343
|
| |
|
|
| |
llvm-svn: 93340
|
| |
|
|
|
|
| |
rewriting for any target. (refixes radar 7530235).
llvm-svn: 93331
|
| |
|
|
| |
llvm-svn: 93328
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
that name constructors, the endless joys of out-of-line constructor
definitions, and various other corner cases that the previous hack
never imagined. Fixes PR5688 and tightens up semantic analysis for
constructor names.
Additionally, fixed a problem where we wouldn't properly enter the
declarator scope of a parenthesized declarator. We were entering the
scope, then leaving it when we saw the ")"; now, we re-enter the
declarator scope before parsing the parameter list.
Note that we are forced to perform some tentative parsing within a
class (call it C) to tell the difference between
C(int); // constructor
and
C (f)(int); // member function
which is rather unfortunate. And, although it isn't necessary for
correctness, we use the same tentative-parsing mechanism for
out-of-line constructors to improve diagnostics in icky cases like:
C::C C::f(int); // error: C::C refers to the constructor name, but
// we complain nicely and recover by treating it as
// a type.
llvm-svn: 93322
|
| |
|
|
| |
llvm-svn: 93320
|
| |
|
|
|
|
|
| |
information to feed diagnostics instead of regenerating it. Much room for
improvement here, but fixes some unfortunate problems reporting on method calls.
llvm-svn: 93316
|
| |
|
|
|
|
|
| |
This now rejects literal operators that don't meet the requirements.
Templates are not yet checked for.
llvm-svn: 93315
|
| |
|
|
| |
llvm-svn: 93314
|