Files
swift-mirror/test/Interpreter/raw_layout_deinit.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

37 lines
681 B
Swift

// RUN: %empty-directory(%t)
// RUN: %target-build-swift -enable-experimental-feature RawLayout %s -o %t/a.out
// RUN: %target-codesign %t/a.out
// RUN: %target-run %t/a.out | %FileCheck %s
// REQUIRES: executable_test
// REQUIRES: swift_feature_RawLayout
@_rawLayout(size: 16, alignment: 16)
struct Foo: ~Copyable {
init(_ value: Int) {
print("Foo.init(\(value))")
}
deinit {
print("Foo.deinit")
}
func bar() {
print("Foo.bar()")
}
}
func test() {
let foo = Foo(42)
foo.bar()
}
print("-- start")
test()
print("-- done")
// CHECK: -- start
// CHECK-NEXT: Foo.init(42)
// CHECK-NEXT: Foo.bar()
// CHECK-NEXT: Foo.deinit
// CHECK-NEXT: -- done