You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 29, 2020. It is now read-only.
In nodejs/node#3401 it's discussed that almost all fs functions assume a Unicode-supporting filesystem, specifically, that char* are in UTF-8. While this is somewhat common (and an ideal) picture, it's not universal. Consider how to work with this issue:
should libuv and/or calls to it detect the encoding and convert?
… with a fast path for environments (OS X, Windows, others?) with a known encoding
The text was updated successfully, but these errors were encountered:
Libuv treats path names as byte arrays (except on Windows) so I don't think libuv is the right place to do conversion, that logic should go into the "representation layer", i.e., node.js.
with a fast path for environments (OS X, Windows, others?) with a known encoding
There is no platform-specific known encoding, it depends on the file system. Libuv probably needs to grow a statvfs(2) binding that lets node.js decide what file system it's dealing with on a per-path basis.
In nodejs/node#3401 it's discussed that almost all fs functions assume a Unicode-supporting filesystem, specifically, that
char*
are in UTF-8. While this is somewhat common (and an ideal) picture, it's not universal. Consider how to work with this issue:The text was updated successfully, but these errors were encountered: