Files
swift-mirror/validation-test/compiler_crashers_fixed/0114-swift-constraints-solution-computesubstitutions.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

40 lines
585 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
protocol l : p {
}
protocol m {
j f = p
}
f m : m {
j f = o
}
func i<o : o, m : m n m.f == o> (l: m) {
}
k: m
}
func p<m>() -> [l<m>] {
return []
}
f
m)
func f<o>() -> (o, o -> o) -> o {
m o m.i = {
}
{
o) {
p }
}
protocol f {
class func i()
}
class m: f{ class func i {}
protocol p {
class func l()
}
class o: p {
class func l() { }