Mark Lacey bc7dff5c9f Revert "Re-instate "Improve disjunction selection"" ...

This reverts commit
ecfa406fc5, which was reinstating
3c5b393e0c.

It does not revert one test change from that commit, because
inexplicably one of the tests is still failing, probably due to some
other changes that have happened since. I'm leaving a ticket open to
investigate.

I've added one of the new cases that is failing as a result of this
change.

This is being reverted not because of bugs in this particular commit,
but because it seems to be exposing other bugs in the type checker that
are resulting in source compatibility problems. We need to shake these
other bugs out of the type checker before bringing this change back.

2017-05-15 11:27:11 -07:00

..

type_checker_crashers

Sema: Fixes for handling of 'Self'-returning methods

2017-01-03 21:49:00 -08:00

type_checker_crashers_fixed

In Swift 3 mode, allow "tuple unsplatting" in certain cases. (#7077)

2017-01-27 11:19:07 -08:00

type_checker_perf_failing

[Constraint solver] Type checker perf test with mixed dictionary/closures.

2017-04-16 09:45:20 -07:00

explicit_coercions.swift

[Constraint solver] Handle disjunctions as separate connected components.

2017-02-20 17:18:18 -08:00

interpolation_placeholders.swift

Replace concrete init(stringInterpolationSegment:)'s with generic ones

2017-02-08 21:01:09 -08:00

OverridesAndOverloads.swift

Rename -parse flag to -typecheck

2016-11-28 10:50:55 -08:00

protocol_typo_correction.swift

Fix the TypeChecker's omitNeedlessWords to use interface types. (#7193)

2017-02-02 14:26:29 -08:00