Fix build warnings in NSOperation #551
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
||
|
|
||
| return other.withUnsafeBytes { (bytes2: UnsafePointer<Void>) -> Bool in | ||
| let bytes1 = bytes |
Member
Author
There was a problem hiding this comment.
UnsafePointer<Void> needs to be replaced by UnsafeRawPointer. But is it applicable to withUnsafeBytes<ResultType, ContentType>(_ body: (UnsafePointer<ContentType>) throws -> ResultType) ?
Contributor
|
The Data parts of this are handled by: #553 (which brings Data+NSData to mostly Swift3 parity). |
Member
Author
|
@michael-lehew : I have reverted the NSData changes from this PR. Thanks. |
pushkarnk
changed the title
Contributor
|
looks good to me; built manually on linux. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.