Files
swift-mirror/test/embedded/stdlib-strings-interpolation.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

36 lines
972 B
Swift

// RUN: %target-run-simple-swift(-Osize -swift-version 5 -enable-experimental-feature Embedded -parse-as-library -runtime-compatibility-version none -wmo) | %FileCheck %s
// REQUIRES: swift_in_compiler
// REQUIRES: executable_test
// REQUIRES: optimized_stdlib
// REQUIRES: OS=macosx || OS=linux-gnu
// REQUIRES: swift_feature_Embedded
@main
struct Main {
static func main() {
let n = 42
let m = -42
let s = "str"
let str = "Hello \(s) \(n) \(s) \(m)"
print(str)
print("hex: \(hex: 42)")
print("ptr: \(UnsafeRawPointer(bitPattern: UInt(0xffff0000))!)")
}
}
extension DefaultStringInterpolation {
mutating func appendInterpolation(hex value: Int) {
appendInterpolation("0x" + String(value, radix: 16))
}
mutating func appendInterpolation(_ value: UnsafeRawPointer) {
appendInterpolation("0x" + String(UInt(bitPattern: value), radix: 16))
}
}
// CHECK: Hello str 42 str -42
// CHECK: hex: 0x2a
// CHECK: ptr: 0xffff0000