Files
swift-mirror/validation-test/compiler_crashers_fixed/0258-swift-constraints-constraintsystem-resolveoverload.swift
Jordan Rose cc45a8e86a [test] Don't run still-crashing compiler_crashers under no-asserts builds.
Per discussion on the list. From now on, when you fix a compiler_crashers
test case, move it to compiler_crashers_fixed so that we get no-asserts and
ASan coverage.

Swift SVN r27055
2015-04-07 03:05:02 +00:00

35 lines
670 B
Swift

// RUN: not %target-swift-frontend %s -parse
// Distributed under the terms of the MIT license
// Test case submitted to project by https://github.com/practicalswift (practicalswift)
// Test case found by fuzzing
import Foundation
class A {
class func a() -> String {
return ""
}
class func b() {
struct c {
static let d: String = {
return self }
}
func b(c) -> <d>(() -> d) {
}
struct d<f(b: c) {
self.b = b
}
}
var f = 1
var e: Int -> Int = {
return $0
}
let d: Int = { c, b in
}(f, e)
import Foundation
extension NSSet {
convenience init<T>(array: Array<T>) {
self.init()
}
}