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

Fix string interoperability problem on using implicitly wchar_t is 16bit #124

Open
kekyo opened this issue Jun 11, 2022 · 2 comments
Open
Labels

Comments

@kekyo
Copy link
Owner

kekyo commented Jun 11, 2022

The entire IL2C relies on wchar_t being 16-bit.
I was completely oblivious to the fact that such an environment is possible...

Related #100

@kekyo kekyo added the bug label Jun 11, 2022
@kekyo
Copy link
Owner Author

kekyo commented Jun 11, 2022

Perhaps it would be better to introduce a type like char16_t so that it is always 16bit. However, because of the string literal problem, it cannot be said that simply defining a type and replacing it is sufficient, and it would be a bit involved in the discussion of whether to treat internally System.String as UTF8 or not.

Past related:

@NCLnclNCL
Copy link

Hello

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

No branches or pull requests

2 participants