Files
swift-mirror/test/embedded/generic-autoclosure.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

34 lines
669 B
Swift

// RUN: %target-swift-frontend -parse-stdlib -emit-ir %s -enable-experimental-feature Embedded -Xllvm -link-embedded-runtime=0
// REQUIRES: swift_in_compiler
// REQUIRES: VENDOR=apple
// REQUIRES: OS=macosx
// REQUIRES: swift_feature_Embedded
public struct UInt23 {
}
public protocol MyBinaryInteger {
}
extension UInt23: MyBinaryInteger {
}
protocol MyProto {
static var my_static_var: UInt23 { get }
static func foo()
}
struct MyStruct: MyProto {
static let my_static_var = UInt23()
}
extension MyProto {
public static func foo() {
bar(Self.my_static_var)
}
}
public func bar<T: MyBinaryInteger>(_ value: @autoclosure () -> T) {
}