Files
swift-mirror/test/Constraints/implicit_last_exprs_double_cgfloat_conversion.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

63 lines
1023 B
Swift

// RUN: %target-typecheck-verify-swift -enable-experimental-feature ImplicitLastExprResults %clang-importer-sdk
// REQUIRES: objc_interop
// REQUIRES: swift_feature_ImplicitLastExprResults
import Foundation
func testReturn1(_ d: Double) -> CGFloat {
print("hello")
d
}
func testReturn2(_ d: Double) -> CGFloat {
()
if .random() { d } else { 0 }
}
func testReturn3(_ d: CGFloat) -> Double {
print("hello")
switch Bool.random() { case true: d case false: 0 }
}
func testReturn4(_ d: Double) -> CGFloat {
print("hello")
if .random() {
print("hello")
d
} else {
if .random() {
print("hello")
d
} else {
0
}
}
}
func testClosure(_ d: CGFloat) {
func fn(_: () -> Double) {}
fn {
print("hello")
d
}
fn {
print("hello")
if .random() { 0.0 } else { d }
}
fn {
print("hello")
if .random() {
print("hello")
d
} else {
if .random() {
print("hello")
d
} else {
0
}
}
}
}