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.

Sign up for GitHub

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

Jump to bottom

Planning: strings and unicode #36

Open
LB-- opened this issue Nov 2, 2015 · 1 comment
Open

Planning: strings and unicode #36

LB-- opened this issue Nov 2, 2015 · 1 comment
Assignees
@LB--
Labels
planning

Comments

@LB--
Copy link
Member

LB-- commented Nov 2, 2015

There is some good discussion in https://what.thedailywtf.com/t/so-about-strings-and-unicode/52250/

Also, Perl 6 seems to be handling things in the ideal way:
https://6guts.wordpress.com/2015/04/12/this-week-unicode-normalization-many-rts/

Separate types and treatments for bytes, code points, and graphemes.
@LB-- LB-- added the planning label Nov 2, 2015
@LB-- LB-- self-assigned this Nov 2, 2015
@LB--
Copy link
Member Author

LB-- commented Jul 13, 2016 •
edited
Loading

Certainly, UTF-8 will only be used via byte buffers (which are possibly behind a strong type alias) and signed types will be nowhere nearby. Signed code units can die in a fire.

@LB-- LB-- mentioned this issue Jul 13, 2016
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@LB-- LB--

Labels
planning
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@LB--