Files
swift-mirror/validation-test/embedded/rdar126965232.swift
Daniel Rodríguez Troitiño ba68faaed5 [test] Mark tests that use experimental/upcoming features as such
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.
2024-11-02 11:46:46 -07:00

27 lines
724 B
Swift

// RUN: %target-swiftc_driver \
// RUN: -c \
// RUN: %s \
// RUN: -Xfrontend -sil-verify-all \
// RUN: -enable-experimental-feature Embedded \
// RUN: -wmo \
// RUN: -Osize \
// RUN: -o %t/bin
// REQUIRES: swift_in_compiler
// REQUIRES: optimized_stdlib
// REQUIRES: OS=macosx || OS=linux-gnu
// REQUIRES: swift_feature_Embedded
class MyClass {
var x: Int? = nil
var enabled: Bool = true
}
public func app_main() {
let object = MyClass()
while true {
let enabled = object.enabled
object.enabled = !enabled
}
}