Skip to content

Update the ChangeLog message for SE-0107: UnsafeRawPointer. #3969

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 1 commit into from
Aug 3, 2016
Merged

Update the ChangeLog message for SE-0107: UnsafeRawPointer. #3969

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
13 changes: 7 additions & 6 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,12 +4,13 @@ Swift 3.0
---------
* [SE-0107](https://github.com/apple/swift-evolution/blob/master/proposals/0107-unsaferawpointer.md)

An `Unsafe[Mutable]RawPointer` type has been introduced. It
replaces `Unsafe[Mutable]Pointer<Void>`. Conversion from
`UnsafePointer<T>` to `UnsafePointer<U>` has been
disallowed. `Unsafe[Mutable]RawPointer` provides an API for untyped
memory access, and an API for binding memory to a type. Binding
memory allows for safe conversion between pointer types.
An `Unsafe[Mutable]RawPointer` type has been introduced. It replaces
`Unsafe[Mutable]Pointer<Void>`. Conversion from `UnsafePointer<T>`
to `UnsafePointer<U>` has been disallowed. `Unsafe[Mutable]RawPointer`
provides an API for untyped memory access, and an API for binding memory
to a type. Binding memory allows for safe conversion between pointer types.
See `bindMemory(to:capacity:)`, `assumingMemoryBound(to:)`, and
`withMemoryRebound(to:capacity:)`.

* [SE-0096](https://github.com/apple/swift-evolution/blob/master/proposals/0096-dynamictype.md):

Expand Down