-
Notifications
You must be signed in to change notification settings - Fork 10.4k
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.
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
Migrate from UnsafePointer<Void> to UnsafeRawPointer. #3724
Conversation
LGTM. |
There are a few test case failures that I still need to investigate. Such as: |
As proposed in SE-0107: UnsafeRawPointer. `void*` imports as `UnsafeMutableRawPointer`. `const void*` imports as `UnsafeRawPointer`. Occurrences of `UnsafePointer<Void>` are replaced with UnsafeRawPointer.
This requires explicit memory binding in several places, particularly in NSData and CoreAudio.
This is unfortunately necessary for assignment between types imported from C.
// FIXME: Why is this necessary? | ||
@_transparent | ||
public init(_ other: Unsafe${Mutable}RawPointer) { | ||
self._rawValue = other._rawValue |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
self = other
?
@swift-ci Please smoke test OS X. |
Depends on corelibs-libdispatch PR: Depends on corelibs-foundation PR: |
build-toolchain passes on both darwin and linux. |
This reverts commit ece0951. This results in lldb failues on linux that I can't readily debug. Backing out until they can be resolved.
No description provided.