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

Strings #17

Open
Simn opened this issue Jun 27, 2013 · 3 comments
Open

Strings #17

Simn opened this issue Jun 27, 2013 · 3 comments
Assignees

Comments

@Simn
Copy link
Collaborator

Simn commented Jun 27, 2013

No description provided.

@ghost ghost assigned ousado Jun 27, 2013
@Simn Simn mentioned this issue Jun 27, 2013
@Simn
Copy link
Collaborator Author

Simn commented Sep 16, 2013

Could you tell us how far you got with this?

@ousado
Copy link
Collaborator

ousado commented Sep 16, 2013

As far as Unicode is concerned, it should be a straight mapping to the ICU API for the most part. Haven't done it yet.

We need to decide on how we go about strings in general. From what I recall from our conversations on IRC, we postponed that decision. The options were along the lines of having 2+ genc versions, one using neko-style raw, unchecked strings and one using ICU strings and hence UTF-16 internally for the default String type. We also considered another version using UTF-8 internally, which is something ICU also provides limited (compared to UTF-16) support for.
Is that approach too complicated/confusing for the user, prone to introducing incompatibilities?

@Simn
Copy link
Collaborator Author

Simn commented Sep 16, 2013

We could start with the ICU version and then look into optimizing it I suppose.

Simn added a commit that referenced this issue Jun 6, 2014
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

2 participants