5 Commits

Author	SHA1	Message	Date
Hamish Knight	7a137d6756	[CS] Allow ExprPatterns to be type-checked in the solver ... Previously we would wait until CSApply, which would trigger their type-checking in `coercePatternToType`. This caused a number of bugs, and hampered solver-based completion, which does not run CSApply. Instead, form a conjunction of all the ExprPatterns present, which preserves some of the previous isolation behavior (though does not provide complete isolation). We can then modify `coercePatternToType` to accept a closure, which allows the solver to take over rewriting the ExprPatterns it has already solved. This then sets the stage for the complete removal of `coercePatternToType`, and doing all pattern type-checking in the solver.	2023-06-07 00:35:01 +01:00
Holly Borla	0708e0efd4	Revert "Tests: Disable failing SwiftUI validation tests"	2022-11-15 09:10:23 -08:00
Allan Shortlidge	b2421aa463	Tests: Disable failing SwiftUI validation tests until rdar://102298208 is fixed.	2022-11-13 16:56:20 -08:00
Mishal Shah	22f61df98b	Use %target-cpu in the tests to support running on Apple Silicon hardware	2021-04-08 23:26:18 -07:00
Pavel Yaskevich	1d3f3204ca	[ResultBuilders] Account of a fact that re-write of a statement can fail ... If one of the statements in the result builder body fails to apply solution, let's fail entire rewrite attempt, otherwise type-checker would end up with AST that has null pointers for some child nodes. Resolves: rdar://problem/70256351	2020-11-05 16:29:58 -08:00