You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, FTMs like __cpp_lib_filesystem take into account availability markup like _LIBCPP_AVAILABILITY_HAS_NO_FILESYSTEM_LIBRARY. In other words, if the deployment target doesn't support <filesystem> the FTM will reflect that. That's good.
However, FTMs don't reflect carve-outs like _LIBCPP_HAS_NO_FILESYSTEM. In fact, generated tests like libcxx/test/std/language.support/support.limits/support.limits.general/filesystem.version.compile.pass.cpp are disabled with // UNSUPPORTED: no-filesystem, which means that we basically don't test the presence or absence of these FTMs in the case of carved-out configurations.
Instead, FTMs should reflect that the library has been configured without support for X or Y.
The text was updated successfully, but these errors were encountered:
ldionne
added
the
libc++
libc++ C++ Standard Library. Not GNU libstdc++. Not libc++abi.
label
Oct 4, 2023
Currently, FTMs like
__cpp_lib_filesystem
take into account availability markup like_LIBCPP_AVAILABILITY_HAS_NO_FILESYSTEM_LIBRARY
. In other words, if the deployment target doesn't support<filesystem>
the FTM will reflect that. That's good.However, FTMs don't reflect carve-outs like
_LIBCPP_HAS_NO_FILESYSTEM
. In fact, generated tests likelibcxx/test/std/language.support/support.limits/support.limits.general/filesystem.version.compile.pass.cpp
are disabled with// UNSUPPORTED: no-filesystem
, which means that we basically don't test the presence or absence of these FTMs in the case of carved-out configurations.Instead, FTMs should reflect that the library has been configured without support for X or Y.
The text was updated successfully, but these errors were encountered: