Ben Langmuir 69fdca43da Fix assertion failure code completing after nil literal ...

We were asserting (and doing the wrong thing) when trying to code
complete
    nil #^HERE^#

The issue is that we tried to apply a solution to the expression that
contained free type variables (converted to generic parameters). This
trips us up when we expect the new type to conform to protocols. In code
completion we generally only need the type of the expression, so this
commit switches to getting that more explicitly.  That said, this did
cause us to drop non-API parameter names in call patterns after an
opening '(' in some cases (covered by rdar://20962472).

Thanks to Doug for suggesting this solution!

rdar://problem/20891867

Swift SVN r28584

2015-05-14 22:22:37 +00:00

..

CodeCompletionTypeChecking.h

Fix assertion failure code completing after nil literal

2015-05-14 22:22:37 +00:00

SourceLoader.h

Transform the Module class into ModuleDecl.

2015-05-07 21:10:50 +00:00