Ryan Liptak 19b219bc8a Fix windows.CreateSymbolicLink/ReadLink for non-relative paths
This fixes a few things:
- Previously, CreateSymbolicLink would always create a relative link if a `dir` was provided, but the relative-ness of a link should be determined by the target path, not the null-ness of the `dir`.
- Special handling is now done to symlink to 'rooted' paths correctly (they are treated as a relative link, which is different than how the xToPrefixedFileW functions treat them)
- ReadLink now correctly supports UNC paths via a new `ntToWin32Namespace` function which intends to be an analog of `RtlNtPathNameToDosPathName` (RtlNtPathNameToDosPathName is not used because it seems to heap allocate as it takes an RTL_UNICODE_STRING_BUFFER)
2023-08-15 15:52:33 -07:00
..
2023-08-15 14:00:35 -07:00
2023-08-02 12:00:14 -07:00
2023-07-16 18:32:52 -07:00
2023-04-22 13:09:15 +03:00
2023-07-31 03:49:21 -04:00
2023-07-31 10:51:44 -07:00
2023-06-25 14:51:03 -07:00
2023-06-10 20:42:30 -07:00
2023-08-02 12:00:14 -07:00
2023-08-06 18:12:05 +02:00
2023-07-07 11:57:09 -07:00