[4.0] [GSB] Improve handling of concrete types, type aliases, recursion#10565

Merged

tkremenek merged 17 commits intoswiftlang:swift-4.0-branchfrom

DougGregor:gsb-concrete-types-recursion

Jun 26, 2017

Commits on Jun 26, 2017

[GSB] Eliminate PotentialArchetype::NestedTypeUpdate.
DougGregor
committed
[GSB] Separate out a "structurally derived" requirement source kind.
DougGregor
committed
[GSB] Improve handling of conformances resolved by concrete types.
DougGregor
committed
[GSB] Remove unused form of addSameTypeRequirementDirect()
DougGregor
committed
[GSB] Break recursion based on the “root” type we’re creating requirements for.
DougGregor
committed
[GSB] Avoid recursively growing increasingly-nested potential archetypes.
DougGregor
committed
[GSB] Clean up the meaning of ArchetypeResolutionKind::(Complete)WellFormed.
DougGregor
committed
[GSB] Centralize diagnosis of concrete types and conformance requirements.
DougGregor
committed
[GSB] Concretize nested types when merging two potential archetypes.
DougGregor
committed
[GSB] Diagnose all same-type-to-concrete conflicts consistently.
DougGregor
committed
[GSB] Cope with typealiases within protocol hierarchies.
DougGregor
committed
[GSB] When retrieving the archetype anchor, allow partial results.
DougGregor
committed
Add formerly-crashing test case for SR-4786 / rdar://problem/31955862.
DougGregor
committed
[GSB] Don't add invalid concrete requirements.
DougGregor
committed
Add recently-fixed test case from SR-4737 / rdar://problem/31905232.
DougGregor
committed
[GSB] Ensure that we have superclass constraints from merged equiv class.
DougGregor
committed
[GSB] Don't crash when substitution fails to produce a type.
DougGregor
committed