|
1 | 1 | # UTF8Span: Safe UTF-8 Processing Over Contiguous Bytes |
2 | 2 |
|
3 | | -* Proposal: [SE-0464](0464-utf8-span.md) |
| 3 | +* Proposal: [SE-0464](0464-utf8span-safe-utf8-processing.md) |
4 | 4 | * Authors: [Michael Ilseman](https://github.com/milseman), [Guillaume Lessard](https://github.com/glessard) |
5 | 5 | * Review Manager: [Tony Allevato](https://github.com/allevato) |
6 | 6 | * Status: **Active review (March 5–19, 2025)** |
7 | 7 | * Bug: rdar://48132971, rdar://96837923 |
8 | | -* Implementation: https://github.com/swiftlang/swift/pull/78531 |
9 | | -* Review: ([pitch 1](https://forums.swift.org/t/pitch-utf-8-processing-over-unsafe-contiguous-bytes/69715)) ([pitch 2](https://forums.swift.org/t/pitch-safe-utf-8-processing-over-contiguous-bytes/72742)) ([review](https://forums.swift.org/t/se-0464-utf8span-safe-utf-8-processing-over-contiguous-bytes/78307)) |
| 8 | +* Implementation: [swiftlang/swift#78531](https://github.com/swiftlang/swift/pull/78531) |
| 9 | +* Review: ([first pitch](https://forums.swift.org/t/pitch-utf-8-processing-over-unsafe-contiguous-bytes/69715)) ([second pitch](https://forums.swift.org/t/pitch-safe-utf-8-processing-over-contiguous-bytes/72742)) ([third pitch](https://forums.swift.org/t/pitch-utf8span-safe-utf-8-processing-over-contiguous-bytes/77483)) ([review](https://forums.swift.org/t/se-0464-utf8span-safe-utf-8-processing-over-contiguous-bytes/78307)) |
10 | 10 |
|
11 | 11 |
|
12 | 12 | ## Introduction |
13 | 13 |
|
14 | | -We introduce `UTF8Span` for efficient and safe Unicode processing over contiguous storage. `UTF8Span` is a memory safe non-escapable type [similar to `Span`](https://github.com/swiftlang/swift-evolution/pull/2307). |
| 14 | +We introduce `UTF8Span` for efficient and safe Unicode processing over contiguous storage. `UTF8Span` is a memory safe non-escapable type [similar to `Span`](0447-span-access-shared-contiguous-storage.md). |
15 | 15 |
|
16 | 16 | Native `String`s are stored as validly-encoded UTF-8 bytes in an internal contiguous memory buffer. The standard library implements `String`'s API as internal methods which operate on top of this buffer, taking advantage of the validly-encoded invariant and specialized Unicode knowledge. We propose making this UTF-8 buffer and its methods public as API for more advanced libraries and developers. |
17 | 17 |
|
@@ -522,7 +522,7 @@ extension UTF8Span { |
522 | 522 |
|
523 | 523 | ### `UTF8Span` from `String` |
524 | 524 |
|
525 | | -We propose adding `utf8Span` properties to `String` and `Substring`, in line with [SE-0456](https://forums.swift.org/t/se-0456-add-span-providing-properties-to-standard-library-types/77233/17): |
| 525 | +We propose adding `utf8Span` properties to `String` and `Substring`, in line with [SE-0456](0456-stdlib-span-properties.md): |
526 | 526 |
|
527 | 527 | ```swift |
528 | 528 | extension String { |
|
0 commit comments