swift-mirror/validation-test/compiler_crashers/005-recursive-call.swift at 5ad871ecd6a4b40783f190b51a8c62b20e5e86cf - swift-mirror - Gitea: Git with a cup of tea

averello/swift-mirror

mirror of https://github.com/apple/swift.git synced 2025-12-21 12:14:44 +01:00

Files

Joe Pamer fa692976f5 If an expression fails to type check, and there were no failures posted or constraints to mine for a reason, we can be fairly certain that the reason for the failure was a lack of contextual type data. In this case, we should post a diagnostic rather than let the failure slip through. This addresses crash suite scenarios 001, 005, 020 and 045. (rdar://problem/16712071, rdar://problem/17317691, rdar://problem/17317691)

You'll notice that emitting this diagnostic will make some already noisy closure-related errors slightly more so. This is unfortunate, but for the time-being it's better than crashing.

Swift SVN r21817

2014-09-09 23:58:59 +00:00

9 lines

271 B

Swift

Raw Blame History

 // RUN: %swift %s -parse -verify
 // Test case submitted to project by https://github.com/practicalswift (practicalswift)
 class c {
     func b((Any, c))(a: (Any, AnyObject)) {
         b(a) // expected-error{{type of expression is ambiguous without more context}}
     }
 }