Files
swift-mirror/validation-test/compiler_crashers_fixed/1376-swift-parser-parsetoken.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

52 lines
686 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
class a {
protocol b = b(Any) {
class func c<T) -> {
}
}
let t: U) -> {
}
var f : NSObject {
t: d = b() in return self.h = Swift.e = a<T) {
b: b {
class func e> {
}
func g() { c(c : P> {
}
}
var b() {
enum A : Range<T, T : T> U) -> Bool {
}
assert() {
if c {
i<U -> == c(f() -> {
}
class a : String)
}
}
protocol b {
struct S())
}
}
}
}
}
protocol a {
}
class a {
protocol c {
}
protocol a {
}
func c(T.b {
return ".Element>], e(m: A""a!
}
return { c()
}("
func a<S : a)