-
Notifications
You must be signed in to change notification settings - Fork 212
Marshal String Encodings #1283
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
base: master
Are you sure you want to change the base?
Marshal String Encodings #1283
Conversation
|
|
||
| <file name = "src/cpp/encoding/Ascii.cpp"/> | ||
| <file name = "src/cpp/encoding/Utf8.cpp"/> | ||
| <file name = "src/cpp/encoding/Utf16.cpp"/> |
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.
I think it would be better to include these in the build only if the types are actually needed by haxe. They are more like utilities rather than something that should be a mandatory part of the runtime group.
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.
I'll look into it. Another thing I was thinking of was changing string.cpp to use these functions as well since there's a fair bit of duplication here, plus the functions in these classes deal with some things the string.cpp ones don't (various utf-8 ranges are invalid).
I need to check the performance characteristics though, since all these functions are bound checked whereas string.cpp works on raw pointers.
details on haxe side : HaxeFoundation/haxe#12476