mirror of
https://github.com/apple/swift.git
synced 2025-12-14 20:36:38 +01:00
ba68faaed5
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.
31 lines
859 B
Swift
31 lines
859 B
Swift
// RUN: %target-swift-frontend -verify -sil-verify-all -enable-experimental-feature ReferenceBindings -emit-sil %s
|
|
|
|
// REQUIRES: swift_feature_ReferenceBindings
|
|
|
|
func varBindingTest() {
|
|
var x = "1"
|
|
x = "1"
|
|
inout x1 = x // expected-error {{overlapping accesses to 'x', but modification requires exclusive access; consider copying to a local variable}}
|
|
let _ = x1
|
|
inout x2 = x // expected-note {{conflicting access is here}}
|
|
let _ = x2
|
|
}
|
|
|
|
func varBindingTest2() {
|
|
var x = "1"
|
|
x = "1"
|
|
inout x1 = x // expected-error {{overlapping accesses to 'x', but modification requires exclusive access; consider copying to a local variable}}
|
|
let _ = x1
|
|
x = "2" // expected-note {{conflicting access is here}}
|
|
}
|
|
|
|
func varBindingTest3() {
|
|
var x = "1"
|
|
x = "1"
|
|
do {
|
|
inout x1 = x
|
|
let _ = x1
|
|
}
|
|
x = "2"
|
|
}
|