4 Commits

Author	SHA1	Message	Date
Alex Hoppen	e14fa7291f	[CS] Don’t fail constraint generation for ErrorExpr or if type fails to resolve ... Instead of failing constraint generation by returning `nullptr` for an `ErrorExpr` or returning a null type when a type fails to be resolved, return a fresh type variable. This allows the constraint solver to continue further and produce more meaningful diagnostics. Most importantly, it allows us to produce a solution where previously constraint generation for a syntactic element had failed, which is required to type check multi-statement closures in result builders inside the constraint system.	2022-07-20 09:46:12 +02:00
Slava Pestov	5808d9beb9	Parse: Remove parse-time name lookup	2020-11-16 22:39:44 -05:00
Slava Pestov	bd36100cb3	Update tests in preparation for disabling parser lookup ... I created a second copy of each test where the output changes after disabling parser lookup. The primary copy now explicitly calls the frontend with -disable-parser-lookup and expects the new diagnostics; the *_parser_lookup.swift version calls the frontend with -enable-parser-lookup and has the old expectations. This allows us to turn parser lookup on and off by default without disturbing tests. Once parser lookup is completely removed we can remove the *_parser_lookup.swift variants.	2020-10-03 09:37:55 -04:00
Doug Gregor	3e2e81d8a3	Add already-fixed test case from rdar://problem/45557325.	2018-10-29 09:57:39 -07:00