#
090da2d1 |
| 01-Jan-2018 |
Faisal Vali <faisalv@yahoo.com> |
Again reverting an attempt to convert the DeclSpec enums into scoped enums. - reverts r321622, r321625, and r321626. - the use of bit-fields is still resulting in warnings - even though we can us
Again reverting an attempt to convert the DeclSpec enums into scoped enums. - reverts r321622, r321625, and r321626. - the use of bit-fields is still resulting in warnings - even though we can use static-asserts to harden the code and ensure the bit-fields are wide enough. The bots still complain of warnings being seen. - to silence the warnings requires specifying the bit-fields with the underlying enum type (as opposed to the enum type itself), which then requires lots of unnecessary static casts of each enumerator within DeclSpec to the underlying-type, which even though could be seen as implementation details, it does hamper readability - and given the additional litterings, makes me question the value of the change.
So in short - I give up (for now at least).
Sorry about the noise.
llvm-svn: 321628
show more ...
|
#
038df490 |
| 01-Jan-2018 |
Faisal Vali <faisalv@yahoo.com> |
[NFC] Modernize enums TypeSpecifierWidth, TypeSpecifierSign & TypeSpecifierType into scoped enums with underlying types. - Since these enums are used as bit-fields - for the bit-fields to be interp
[NFC] Modernize enums TypeSpecifierWidth, TypeSpecifierSign & TypeSpecifierType into scoped enums with underlying types. - Since these enums are used as bit-fields - for the bit-fields to be interpreted as unsigned, the underlying type must be specified as unsigned.
Previous failed attempt - wherein I did not specify an underlying type - was the sum of: https://reviews.llvm.org/rC321614 https://reviews.llvm.org/rC321615
llvm-svn: 321622
show more ...
|
#
c535adcf |
| 01-Jan-2018 |
Faisal Vali <faisalv@yahoo.com> |
Revert r321614 and r321615 - the enum changes to TypeSpecifierType are breaking some tests - and will require a more careful integration.
Sorry about rushing these changes - thought I could sneak
Revert r321614 and r321615 - the enum changes to TypeSpecifierType are breaking some tests - and will require a more careful integration.
Sorry about rushing these changes - thought I could sneak them in prior to heading out for new years ;)
llvm-svn: 321616
show more ...
|
#
8736dee0 |
| 01-Jan-2018 |
Faisal Vali <faisalv@yahoo.com> |
[NFC] Modernize enums TypeSpecifierWidth, TypeSpecifierSign & TypeSpecifierType into scoped enums.
llvm-svn: 321614
|
#
421b2d1d |
| 29-Dec-2017 |
Faisal Vali <faisalv@yahoo.com> |
[NFC] Modernize enum Declarator::TheContext to a type-safe scoped enum.
Note, we don't do any bitwise manipulations when using them.
llvm-svn: 321546
|
#
f3b3ccda |
| 19-Dec-2017 |
Adrian Prantl <aprantl@apple.com> |
Silence a bunch of implicit fallthrough warnings
llvm-svn: 321115
|
#
acfa339e |
| 17-Dec-2017 |
Benjamin Kramer <benny.kra@googlemail.com> |
Refactor overridden methods iteration to avoid double lookups.
Convert most uses to range-for loops. No functionality change intended.
llvm-svn: 320954
|
#
fead6ae6 |
| 13-Dec-2017 |
Eric Liu <ioeric@google.com> |
[Sema] Ignore decls in namespaces when global decls are not wanted.
Summary: ... in qualified code completion and decl lookup.
Reviewers: ilya-biryukov, arphaman
Reviewed By: ilya-biryukov
Subscr
[Sema] Ignore decls in namespaces when global decls are not wanted.
Summary: ... in qualified code completion and decl lookup.
Reviewers: ilya-biryukov, arphaman
Reviewed By: ilya-biryukov
Subscribers: cfe-commits
Differential Revision: https://reviews.llvm.org/D40562
llvm-svn: 320563
show more ...
|
#
06d34028 |
| 12-Dec-2017 |
Eric Liu <ioeric@google.com> |
[SemaCodeComplete] Allow passing out scope specifiers in qualified-id completions via completion context.
Reviewers: ilya-biryukov, arphaman
Reviewed By: arphaman
Subscribers: nik, cfe-commits
Di
[SemaCodeComplete] Allow passing out scope specifiers in qualified-id completions via completion context.
Reviewers: ilya-biryukov, arphaman
Reviewed By: arphaman
Subscribers: nik, cfe-commits
Differential Revision: https://reviews.llvm.org/D40563
llvm-svn: 320471
show more ...
|
Revision tags: llvmorg-5.0.1, llvmorg-5.0.1-rc3, llvmorg-5.0.1-rc2 |
|
#
f3df1f7b |
| 14-Nov-2017 |
Alex Lorenz <arphaman@gmail.com> |
[completion] complete ObjC interface names in an expression
Objective-C interfaces can be used in a class property expression.
rdar://26982192
llvm-svn: 318129
|
#
b5da91c8 |
| 08-Nov-2017 |
Ilya Biryukov <ibiryukov@google.com> |
Avoid printing some redundant name qualifiers in completion
Summary: Adjusted PrintingPolicy inside code completion to avoid printing some redundant name qualifiers.
Before this change, typedefs th
Avoid printing some redundant name qualifiers in completion
Summary: Adjusted PrintingPolicy inside code completion to avoid printing some redundant name qualifiers.
Before this change, typedefs that were written unqualified in source code were printed with qualifiers in completion. For example, in the following code
struct foo { typedef int type; type method(); };
completion item for `method` had return type of `foo::type`, even though the original code used `type` without qualifiers. After this change, the completion item has return type `type`, as originally written in the source code.
Note that this change does not suppress qualifiers written by the user. For example, in the following code
typedef int type; struct foo { typedef int type; ::type method(foo::type); };
completion item for `method` has return type of `::type` and parameter type of `foo::type`, as originally written in the source code.
Reviewers: arphaman, bkramer, klimek
Reviewed By: arphaman
Subscribers: mgorny, eraman, cfe-commits
Differential Revision: https://reviews.llvm.org/D38538
llvm-svn: 317677
show more ...
|
Revision tags: llvmorg-5.0.1-rc1 |
|
#
13d9054d |
| 27-Oct-2017 |
Ivan Donchevskii <ivan.donchevskii@qt.io> |
Test commit
llvm-svn: 316758
|
#
e3962aeb |
| 26-Oct-2017 |
Benjamin Kramer <benny.kra@googlemail.com> |
Fix overloaded static functions in SemaCodeComplete
https://bugs.llvm.org/show_bug.cgi?id=33904 Happens when static function is accessed via the class variable. That leads to incorrect overloads num
Fix overloaded static functions in SemaCodeComplete
https://bugs.llvm.org/show_bug.cgi?id=33904 Happens when static function is accessed via the class variable. That leads to incorrect overloads number because the variable is considered as the first argument.
struct Bar { static void foo(); static void foo(int); };
int main() { Bar b; b.foo(/*complete here*/); // did not work before Bar::foo(/*complete here*/); // worked fine }
Patch by Ivan Donchevskii!
Differential Revision: https://reviews.llvm.org/D36390
llvm-svn: 316646
show more ...
|
#
b874042e |
| 24-Oct-2017 |
Alex Lorenz <arphaman@gmail.com> |
[code completion] Complete ObjC methods in @implementation without leading '-'/'+' prefix
rdar://12040840
llvm-svn: 316458
|
#
6524c05d |
| 24-Oct-2017 |
Erik Verbruggen <erikjv@me.com> |
Do not add a colon chunk to the code completion of class inheritance access modifiers
With enabled CINDEXTEST_CODE_COMPLETE_PATTERNS env option (which enables IncludeCodePatterns in completion optio
Do not add a colon chunk to the code completion of class inheritance access modifiers
With enabled CINDEXTEST_CODE_COMPLETE_PATTERNS env option (which enables IncludeCodePatterns in completion options) code completion after colon currently suggests access modifiers with 2 completion chunks which is incorrect.
Example: class A : <Cursor>B { }
Currently we get 'NotImplemented:{TypedText public}{Colon :} (40)' but the correct line is just 'NotImplemented:{TypedText public} (40)'
The fix introduces more specific scope that occurs between ':' and '{' It allows us to determine when we don't need to add ':' as a second chunk to the public/protected/private access modifiers.
Patch by Ivan Donchevskii!
Differential Revision: https://reviews.llvm.org/D38618
llvm-svn: 316436
show more ...
|
#
67ef14fe |
| 26-Sep-2017 |
Richard Smith <richard-llvm@metafoo.co.uk> |
Resolve a defect in C++17 copy omission.
When selecting constructors for initializing an object of type T from a single expression of class type U, also consider conversion functions of U that conve
Resolve a defect in C++17 copy omission.
When selecting constructors for initializing an object of type T from a single expression of class type U, also consider conversion functions of U that convert to T (rather than modeling such conversions as calling a conversion function and then calling a constructor).
This approach is proposed as the resolution for the defect, and is also already implemented by GCC.
llvm-svn: 314231
show more ...
|
#
4e7a6fef |
| 22-Sep-2017 |
Ilya Biryukov <ibiryukov@google.com> |
Set completion priority of destructors and operators to CCP_Unlikely.
Summary: It will move destructors and operators to the end of completion list. Destructors and operators are currently very high
Set completion priority of destructors and operators to CCP_Unlikely.
Summary: It will move destructors and operators to the end of completion list. Destructors and operators are currently very high on the completion list, as they have the same priority as member functions. However, they are clearly not something users usually choose in completion lists.
Reviewers: arphaman, erikjv, bkramer, krasimir
Reviewed By: arphaman
Subscribers: eraman, klimek, cfe-commits
Differential Revision: https://reviews.llvm.org/D38081
llvm-svn: 314019
show more ...
|
#
7ec9107f |
| 08-Sep-2017 |
Erik Verbruggen <erikjv@me.com> |
Don't show deleted function (constructor) candidates for code completion
In case of copy constructor is implicitly deleted it's still shown. PR34402 describes a way to reproduce that.
Patch by Ivan
Don't show deleted function (constructor) candidates for code completion
In case of copy constructor is implicitly deleted it's still shown. PR34402 describes a way to reproduce that.
Patch by Ivan Donchevskii!
Differential Revision: https://reviews.llvm.org/D37435
llvm-svn: 312785
show more ...
|
Revision tags: llvmorg-5.0.0, llvmorg-5.0.0-rc5, llvmorg-5.0.0-rc4, llvmorg-5.0.0-rc3, llvmorg-5.0.0-rc2, llvmorg-5.0.0-rc1 |
|
#
b6d1ec80 |
| 21-Jul-2017 |
Ilya Biryukov <ibiryukov@google.com> |
Fixed failing assert in code completion.
Summary: The code was accessing uninstantiated default argument. This resulted in failing assertion at ParmVarDecl::getDefaultArg().
Reviewers: erikjv, klim
Fixed failing assert in code completion.
Summary: The code was accessing uninstantiated default argument. This resulted in failing assertion at ParmVarDecl::getDefaultArg().
Reviewers: erikjv, klimek, bkramer, krasimir
Reviewed By: krasimir
Subscribers: cfe-commits
Differential Revision: https://reviews.llvm.org/D35682
llvm-svn: 308722
show more ...
|
#
797980e0 |
| 19-Jul-2017 |
Erik Verbruggen <erikjv@me.com> |
Fix compilation problem introduced in r308433
llvm-svn: 308438
|
#
11338c59 |
| 19-Jul-2017 |
Erik Verbruggen <erikjv@me.com> |
Add default values for function parameter chunks
Append optional chunks with their default values. For example: before - "int i", after - "int i = 10"
Patch by Ivan Donchevskii! Differential R
Add default values for function parameter chunks
Append optional chunks with their default values. For example: before - "int i", after - "int i = 10"
Patch by Ivan Donchevskii! Differential Revision: https://reviews.llvm.org/D33644
llvm-svn: 308433
show more ...
|
#
ac506d74 |
| 17-Jul-2017 |
Faisal Vali <faisalv@yahoo.com> |
[NFC] Refactor the Preprocessor function that handles Macro definitions and rename Arguments to Parameters in Macro Definitions. - Extracted the reading of the tokens out into a separate function.
[NFC] Refactor the Preprocessor function that handles Macro definitions and rename Arguments to Parameters in Macro Definitions. - Extracted the reading of the tokens out into a separate function. - Replace 'Argument' with 'Parameter' when referring to the identifiers of the macro definition (as opposed to the supplied arguments - MacroArgs - during the macro invocation).
This is in preparation for submitting patches for review to implement __VA_OPT__ which will otherwise just keep lengthening the HandleDefineDirective function and making it less comprehensible.
I will also directly update some extra clang tooling that is broken by the change from Argument to Parameter.
Hopefully the bots will stay appeased.
Thanks!
llvm-svn: 308190
show more ...
|
#
0e54e567 |
| 17-Jul-2017 |
Faisal Vali <faisalv@yahoo.com> |
Revert changes from my previous refactoring - will need to fix dependencies in clang's extra tooling (such as clang-tidy etc.).
Sorry about that.
llvm-svn: 308158
|
#
11746b05 |
| 17-Jul-2017 |
Faisal Vali <faisalv@yahoo.com> |
[NFC] Refactor the Preprocessor function that handles Macro definitions and rename Arguments to Parameters in Macro Definitions. - Extracted the reading of the tokens out into a separate function.
[NFC] Refactor the Preprocessor function that handles Macro definitions and rename Arguments to Parameters in Macro Definitions. - Extracted the reading of the tokens out into a separate function. - Replace 'Argument' with 'Parameter' when referring to the identifiers of the macro definition (as opposed to the supplied arguments - MacroArgs - during the macro invocation).
This is in preparation for submitting patches for review to implement __VA_OPT__ which will otherwise just keep lengthening the HandleDefineDirective function and making it less comprehensible.
Thanks!
llvm-svn: 308157
show more ...
|
#
8a7a4cfa |
| 15-Jun-2017 |
Alex Lorenz <arphaman@gmail.com> |
[Completion] Code complete the members for a dependent type after a '::'
This commit is a follow up to r302797 which added support for dependent completions after the '.' and '->' operators. This co
[Completion] Code complete the members for a dependent type after a '::'
This commit is a follow up to r302797 which added support for dependent completions after the '.' and '->' operators. This commit adds support for dependent completions after the '::' operator.
Differential Revision: https://reviews.llvm.org/D34173
llvm-svn: 305511
show more ...
|