Skip to content

Commit 69d0662

Browse files
hborlashahmishal
andcommitted
Update _posts/2025-NN-NN-swift-6.2-released.md
Co-authored-by: Mishal Shah <[email protected]>
1 parent 25dbe06 commit 69d0662

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

_posts/2025-NN-NN-swift-6.2-released.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,7 @@ The new [`Span`](https://developer.apple.com/documentation/swift/span?changes=_8
4848
Swift 6.2 enhances its capabilities for low-level and security-critical projects beyond new APIs:
4949

5050
* **Embedded Swift:** Embedded Swift now includes Swift’s full `String` APIs, `any` types for class-constrained protocols, and the new `InlineArray` and `Span` types.
51-
* **Safe C++ interoperability:** Projects that mix Swift and C++ can [take advantage of Swift’s safe abstractions](https://www.swift.org/documentation/cxx-interop/safe-interop/) like `Span` for C++ APIs through header annotations.
51+
* **Safe C++ interoperability:** Projects that mix Swift and C++ can [take advantage of Swift’s safe abstractions](/documentation/cxx-interop/safe-interop/) like `Span` for C++ APIs through header annotations.
5252
* **Opt-in strict memory safety:** Swift has provided memory safety since its inception, while allowing use of unsafe constructs like unsafe pointers when needed, such as using a C API that accepts pointers. Swift 6.2 introduces *opt-in strict memory safety*, which flags uses of unsafe constructs, so you can replace them with safe alternatives or explicitly acknowledge them in source code. It’s opt-in because the majority of projects don’t need this level of enforcement — strict memory safety is best left for projects with the strongest security requirements.
5353

5454
## Streamlined Workflows

0 commit comments

Comments
 (0)