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

Support exposing &[u16] as std::u16string_view and u16 as char16_t #240

Closed
hsivonen opened this issue Aug 26, 2022 · 2 comments
Closed

Support exposing &[u16] as std::u16string_view and u16 as char16_t #240

hsivonen opened this issue Aug 26, 2022 · 2 comments

Comments

@hsivonen
Copy link

In text-oriented Rust code like ICU4X, &[u16] is used for UTF-16 and, therefore, has std::u16string_view semantics, and u16 is used for UTF-16 code unit and, therefore, has char16_t semantics. Add configuration options to have these types generated for C++.

@Manishearth
Copy link
Contributor

Manishearth commented Aug 26, 2022

We definitely use u16 for non char16_t reasons in ICU4X, fwiw

Slices are fine though

@robertbastian
Copy link
Collaborator

#367 #368

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

3 participants