mirror of
https://github.com/apple/swift.git
synced 2025-12-21 12:14:44 +01:00
2de9f4a8f5
Since we infer unsafety from a use of a declaration that involves unsafe types in its signature, there isn't a reason to require @unsafe on declaration to restate it. This matches recent revisions of SE-0458.
23 lines
996 B
Swift
23 lines
996 B
Swift
// RUN: %target-typecheck-verify-swift -enable-experimental-feature WarnUnsafe
|
|
|
|
// Make sure everything compiles without error when unsafe code is allowed.
|
|
// RUN: %target-swift-frontend -typecheck -enable-experimental-feature AllowUnsafeAttribute -warnings-as-errors %s
|
|
|
|
// REQUIRES: swift_feature_AllowUnsafeAttribute
|
|
// REQUIRES: swift_feature_WarnUnsafe
|
|
|
|
func test(
|
|
x: OpaquePointer,
|
|
other: UnsafeMutablePointer<Int>
|
|
) {
|
|
var array = [1, 2, 3]
|
|
// expected-warning@+2{{expression uses unsafe constructs but is not marked with 'unsafe'}}{{3-3=unsafe }}
|
|
// expected-note@+1{{reference to instance method 'withUnsafeBufferPointer' involves unsafe type 'UnsafeBufferPointer<Int>'}}
|
|
array.withUnsafeBufferPointer{ buffer in
|
|
// expected-warning@+1{{expression uses unsafe constructs but is not marked with 'unsafe'}}{{5-5=unsafe }}
|
|
print(buffer) // expected-note{{reference to parameter 'buffer' involves unsafe type 'UnsafeBufferPointer<Int>'}}
|
|
}
|
|
array.append(4)
|
|
_ = array
|
|
}
|