5 Commits

Author	SHA1	Message	Date
practicalswift	6d1ae2a39c	[gardening] 2016 → 2017	2017-01-06 16:41:22 +01:00
Jordan Rose	49e6c06eef	[validation-test] Remove "REQUIRES: asserts" from /fixed/ crash cases. (#6156)	2016-12-08 19:06:32 -08:00
David Farler	b7d17b25ba	Rename -parse flag to -typecheck ... A parse-only option is needed for parse performance tracking and the current option also includes semantic analysis.	2016-11-28 10:50:55 -08:00
practicalswift	797b80765f	[gardening] Use the correct base URL (https://swift.org) in references to the Swift website ... Remove all references to the old non-TLS enabled base URL (http://swift.org)	2016-11-20 17:36:03 +01:00
Mark Lacey	dc7d433a40	Remove an overzealous assert. ... When we are able to type check an expression this assert is fine, although of little value. In the context of failed type checks, though, it can be actively harmful. The issue is that we can attempt to solve smaller parts of the constraint system and assign contextual types (e.g. for the arguments of a function) despite not being able to drill into members. Some of the diagnostics we emit in these cases are not terribly useful, and I've opened rdar://problem/27982012 with one example. Resolves: rdar://problem/25812474 rdar://problem/26589865 rdar://problem/27974638	2016-08-23 21:58:29 -07:00