File: StringIndex_bincompat.swift

package info (click to toggle)
swiftlang 6.1.3-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 2,791,532 kB
  • sloc: cpp: 9,901,743; ansic: 2,201,431; asm: 1,091,827; python: 308,252; objc: 82,166; f90: 80,126; lisp: 38,358; pascal: 25,559; sh: 20,429; ml: 5,058; perl: 4,745; makefile: 4,484; awk: 3,535; javascript: 3,018; xml: 918; fortran: 664; cs: 573; ruby: 396
file content (29 lines) | stat: -rw-r--r-- 1,108 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
// RUN: %empty-directory(%t)
// RUN: %target-build-swift -g %s -o %t/StringIndex
// RUN: %target-codesign %t/StringIndex
// RUN: env %env-SWIFT_BINARY_COMPATIBILITY_VERSION=0x050600 %target-run %t/StringIndex %S/Inputs/

// REQUIRES: executable_test
// UNSUPPORTED: freestanding
// UNSUPPORTED: use_os_stdlib || back_deployment_runtime
// UNSUPPORTED: swift_stdlib_asserts

// In 5.7, a number of String APIs started performing stronger index validation,
// eliminating issues such as out of bounds memory accesses when members are
// given invalid indices. The environment variable
// SWIFT_BINARY_COMPATIBILITY_VERSION above forces the stdlib's bincompat
// version to 5.6 so that we can test older behavior.
//
// We can only test old behavior that doesn't lead to undefined behavior,
// though.

import StdlibUnittest

var suite = TestSuite("StringIndexBinCompatTests")
defer { runAllTests() }

suite.test("String.index(before:) on an index near the start") {
  let string = "😲 hi"
  let i = string.utf8.index(after: string.utf8.startIndex)
  expectEqual(string.index(before: i), string.startIndex)
}