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.
22 lines
447 B
Swift
22 lines
447 B
Swift
// REQUIRES: OS=macosx
|
|
// REQUIRES: swift_interpreter
|
|
// REQUIRES: swift_feature_LazyImmediate
|
|
// RUN: %target-jit-run %s -enable-experimental-feature LazyImmediate | %FileCheck %s
|
|
|
|
// Tests that the linkage of private symbols is
|
|
// promoted to hidden external, allowing
|
|
// single-function compilation of non-public symbols.
|
|
|
|
fileprivate func foo() {
|
|
print("foo")
|
|
}
|
|
|
|
func bar() {
|
|
foo()
|
|
print("bar")
|
|
}
|
|
|
|
// CHECK: foo
|
|
// CHECK-NEXT: bar
|
|
bar()
|