Skip to content

[SE-0456] Clarifications #2665

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jan 22, 2025
Merged

[SE-0456] Clarifications #2665

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e5d32c4
[SE-0456] Clarify UnsafeBufferPointer invariants
glessard Jan 18, 2025
bd1d82d
[SE-0456] Clarify “Implications on adoption”
glessard Jan 22, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions proposals/0456-stdlib-span-properties.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -179,7 +179,7 @@ extension UnsafeMutableRawBufferPointer {
}
```

All of these unsafe conversions return a value whose lifetime is dependent on the _binding_ of the UnsafeBufferPointer. Note that this does not keep the underlying memory alive, as usual where the `UnsafePointer` family of types is involved. The programmer must ensure the following invariants for as long as the `Span` or `RawSpan` binding is valid:
All of these unsafe conversions return a value whose lifetime is dependent on the _binding_ of the UnsafeBufferPointer. This dependency does not keep the underlying memory alive. As is usual where the `UnsafePointer` family of types is involved, the programmer must ensure the memory remains allocated while it is in use. Additionally, the following invariants must remain true for as long as the `Span` or `RawSpan` value exists:

- The underlying memory remains initialized.
- The underlying memory is not mutated.
Expand Down Expand Up @@ -220,7 +220,7 @@ This proposal is additive and ABI-compatible with existing code.

## Implications on adoption

The additions described in this proposal require a new version of the Swift standard library and runtime.
The additions described in this proposal require a version of the Swift standard library which include the `Span` and `RawSpan` types.

## Alternatives considered

Expand Down