e4f62e4608
* It is tough to contribute to a project that doesn't use a formatter, * It is extra hard to contribute to a project which has configured the formatter, but ignores it for some files * Code formatting makes it harder to hide obscure / weird bugs by accident or on purpose, Let's rip the bandaid off? Note that PRs currently in flight should be able to be merged relatively easily by applying `clang-format` to their tip prior to merge.
42 lines
1.4 KiB
C++
42 lines
1.4 KiB
C++
#include <algorithm>
|
|
#include <codecvt>
|
|
#include <iostream>
|
|
#include <locale>
|
|
|
|
#include "nix/util/file-path.hh"
|
|
#include "nix/util/file-path-impl.hh"
|
|
#include "nix/util/util.hh"
|
|
|
|
namespace nix {
|
|
|
|
std::optional<std::filesystem::path> maybePath(PathView path)
|
|
{
|
|
if (path.length() >= 3 && (('A' <= path[0] && path[0] <= 'Z') || ('a' <= path[0] && path[0] <= 'z'))
|
|
&& path[1] == ':' && WindowsPathTrait<char>::isPathSep(path[2])) {
|
|
std::filesystem::path::string_type sw = string_to_os_string(std::string{"\\\\?\\"} + path);
|
|
std::replace(sw.begin(), sw.end(), '/', '\\');
|
|
return sw;
|
|
}
|
|
if (path.length() >= 7 && path[0] == '\\' && path[1] == '\\' && (path[2] == '.' || path[2] == '?')
|
|
&& path[3] == '\\' && ('A' <= path[4] && path[4] <= 'Z') && path[5] == ':'
|
|
&& WindowsPathTrait<char>::isPathSep(path[6])) {
|
|
std::filesystem::path::string_type sw = string_to_os_string(path);
|
|
std::replace(sw.begin(), sw.end(), '/', '\\');
|
|
return sw;
|
|
}
|
|
return std::optional<std::filesystem::path::string_type>();
|
|
}
|
|
|
|
std::filesystem::path pathNG(PathView path)
|
|
{
|
|
std::optional<std::filesystem::path::string_type> sw = maybePath(path);
|
|
if (!sw) {
|
|
// FIXME why are we not using the regular error handling?
|
|
std::cerr << "invalid path for WinAPI call [" << path << "]" << std::endl;
|
|
_exit(111);
|
|
}
|
|
return *sw;
|
|
}
|
|
|
|
} // namespace nix
|