It's safe to assume FilePath::CharType == char in platform2
where we don't have to worry about Windows.
With this assumption, the code can be simplified:
- constexpr base::FilePath::CharType kRunContainersPath[] =
- FILE_PATH_LITERAL("/run/containers");
+ constexpr char kRunContainersPath[] = "/run/containers";
Besides, some code in platform2 already assumes FilePath::CharType == char [1], while some code tries not to (thus using FILE_PATH_LITERAL, etc.).
We can remove the inconsistency by assuming FilePath::CharType == char everywhere in platform2
[1] Many FilePath objects are created without FILE_PATH_LITERAL:
% git grep 'FilePath("' |wc -l
310
Context: https://groups.google.com/a/chromium.org/forum/#!topic/chromium-os-dev/lMNs2sazeD4
Comment 1 by bugdroid1@chromium.org
, Aug 6