Details
- Reviewers
• Quuxplusone curdeius - Group Reviewers
Restricted Project - Commits
- rG3a11a41795be: [libcxx] [test] Don't test CharFile (/dev/null) on windows
Diff Detail
- Repository
- rG LLVM Github Monorepo
Unit Tests
Event Timeline
libcxx/test/std/input.output/filesystems/fs.op.funcs/fs.op.status/status.pass.cpp | ||
---|---|---|
116–117 | You might adjust this comment to // file_type::block is tested elsewhere, just so that people don't assume it's related to the #ifndef on the next line. |
Have you heard of nul special file on Windows?
https://gcc.gnu.org/legacy-ml/gcc-patches/2005-05/msg01793.html
I haven't tested it yet but maybe using it on Win instead of /dev/null might be a good idea?
Good point, but neither our implementation nor the MS STL one actually identify files as file_type::character, see https://github.com/microsoft/STL/blob/main/stl/inc/filesystem#L1882 which says:
character, // not used in this implementation; theoretically some special files like CON might qualify, but querying for this is extremely expensive and unlikely to be useful in practice
libcxx/test/std/input.output/filesystems/fs.op.funcs/fs.op.status/status.pass.cpp | ||
---|---|---|
116–117 | Sure, I can do that. |
LGTM. Could you put a similar comment (but concerning only Windows of course) near file_type::character declaration as well?
You might adjust this comment to // file_type::block is tested elsewhere, just so that people don't assume it's related to the #ifndef on the next line.
(And ditto in the other test file, as well.)