Skip to content
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

Investigate Swift 5 String Performance #36

Open
benpious opened this issue Nov 26, 2018 · 0 comments
Open

Investigate Swift 5 String Performance #36

benpious opened this issue Nov 26, 2018 · 0 comments

Comments

@benpious
Copy link
Collaborator

In Swift 5 String will use UTF-8 instead of UTF-16, which means that it won't need to do allocations to access the raw buffer for strtod, and converting from XMLChar buffers will be cheaper. We may be able to get rid of XMLString as a result.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant