Workaround for parseString to support NSString; #68
Conversation
This file contains 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
AliSoftware
approved these changes
Oct 4, 2017
|
@Antondomashnev feel free to merge this yourself as soon as the CI is green 👍 |
|
@AliSoftware I don't have rights to merge it 😄 |
|
Oh, sorry… well you have now, just added you as a Core Contributor (I though I did it already, my bad) 😉 |
|
@AliSoftware thanks 👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Apparently
NSStringis not bridged toLosslessStringConvertiblealthough it's bridged toStringandStringconforms toLosslessStringConvertible😞FYI there is an open ticket for Swift to track the progress.