Skip to content

Support extended characters in pathnames #1603

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

Merged
merged 5 commits into from
Jun 24, 2024
Merged

Support extended characters in pathnames #1603

merged 5 commits into from
Jun 24, 2024

Conversation

Bike
Copy link
Member

@Bike Bike commented Jun 24, 2024

Fixes #1595

Bike added 5 commits June 17, 2024 12:55
Note that this is NOT a complete solution to #1595, as the actual
OS interface (calls to open(3), etc.) is not really prepared for
non-base-strings. It will probably have to do some encoding.
Since they are codepoints in UTF-32. This will HOPEFULLY make a few
parts of using C++ easier, like making pathnames.

This makes the error message when reading dense arrays wrong very
slightly worse, but that's an implementation-specific thing anyway.
Fixes #1595

There's a lot of get_std_string lurking around though. There might
be a couple more holes.
Respecting extended characters, at least
@Bike Bike merged commit 773b236 into main Jun 24, 2024
8 checks passed
@Bike Bike deleted the unicode-pathname branch June 24, 2024 23:18
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

Successfully merging this pull request may close these issues.

parse-namestring doesn't accept unicode
1 participant