Open blowekamp opened 3 months ago
@blowekamp Very interesting, thanks! I definitely like having a separate type for file paths, rather than just "std::string", for improved type safety. I'm also curious to see if it does improve non-ASCII character support in file names, on Windows.
It looks like adopting std::filesystem
would require increasing ITK's minimum macOS to 10.15:
Even though C++17 compilers exist on older version of macOS, the STL shipped on older versions does not support std::filesystem
, from what I gather.
That would suck for me, I still support back to 10.13.
I still support back to 10.13.
Our Python packages also require 10.11.
Add std::filesystem::path to ImageIOBase for eventual wchar support for paths.
This proposes an approach to remove direct access to m_FileName, with the eventual end goal to use GetFilePath and "legacy" GetFileName methods.