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
That was done intentionally as Windows should correctly handle both \ and / as path separators (/ are canonicalized to \) and using / as the separator seemed an easier option.
Are there any cases where it works incorrectly? Or it's mostly about SystemPathSeparator itself being non-canonical for Windows?
Completely understandable if it was internal, but it is a part of the public API. Anyone from commonMain relying on SystemPathSeparator would "assume" that it delegates to the actual system path separator (like Jvm and Js are doing).
If nativeMain is in conflict with the actual system's path separator, why not drop the expect/actual and define SystemPathSeparator in commonMain as /?
SystemPathSeparator
is defined innativeMain
The text was updated successfully, but these errors were encountered: