mirror of
https://github.com/apple/swift.git
synced 2025-12-14 20:36:38 +01:00
ba68faaed5
Find all the usages of `--enable-experimental-feature` or `--enable-upcoming-feature` in the tests and replace some of the `REQUIRES: asserts` to use `REQUIRES: swift-feature-Foo` instead, which should correctly apply to depending on the asserts/noasserts mode of the toolchain for each feature. Remove some comments that talked about enabling asserts since they don't apply anymore (but I might had miss some). All this was done with an automated script, so some formatting weirdness might happen, but I hope I fixed most of those. There might be some tests that were `REQUIRES: asserts` that might run in `noasserts` toolchains now. This will normally be because their feature went from experimental to upcoming/base and the tests were not updated.
47 lines
916 B
Swift
47 lines
916 B
Swift
// REQUIRES: OS=macosx
|
|
// REQUIRES: swift_interpreter
|
|
// RUN: %target-jit-run %s -enable-experimental-feature LazyImmediate | %FileCheck %s
|
|
|
|
// REQUIRES: rdar118189728
|
|
// REQUIRES: swift_feature_LazyImmediate
|
|
|
|
// Tests that parsing of function bodies is deferred
|
|
// to runtime when the interpreter is invoked using
|
|
// experimental lazy compilation. Syntax errors in
|
|
// functions not executed at runtime should be ignored.
|
|
|
|
public func foo() {
|
|
3 +
|
|
}
|
|
|
|
// Syntax error in `foo` should be ignored
|
|
|
|
// CHECK: hello
|
|
print("hello")
|
|
|
|
public func bar(_ b: Bool) {
|
|
if b {
|
|
print("bar")
|
|
} else {
|
|
foo()
|
|
}
|
|
}
|
|
|
|
// Function `foo` with syntax error is not executed
|
|
// by bar, so the type error should again be ignored
|
|
|
|
// CHECK: bar
|
|
bar(true)
|
|
|
|
public func add(_ x: Int, _ y: Int, _ z: Int) -> Int {
|
|
return x + y + z
|
|
}
|
|
|
|
public func sub(_ x: Int, _ y: Int) -> Int {
|
|
return add(x,
|
|
}
|
|
|
|
// CHECK: 6
|
|
print(add(1, 2, 3))
|
|
|