[libc++] Make <print> work without deployment target requirement #75225
Description
In a follow-up, we could use
_LIBCPP_AVAILABILITY_HAS_PRINTto check whether we have__get_ostream_fileon the current deployment target. If we don't, we could instead assume that!__fileand use__vprint_nonunicode. That would make this mostly work for older deployment targets, except for theflushbelow. But by and far, users could use<print>on older deployment targets with no issues.We could then even remove the availability annotations on
__vprint_unicodeand others, since they would basically have no deployment target requirements anymore.
Originally posted by @ldionne in #73262 (comment)
Metadata
Metadata
Assignees
Labels
Type
Projects
Milestone
Relationships
Participants
Activity
[-]In a follow-up, we could use `_LIBCPP_AVAILABILITY_HAS_PRINT` to check whether we have `__get_ostream_file` on the current deployment target. If we don't, we could instead assume that `!__file` and use `__vprint_nonunicode`. That would make this *mostly* work for older deployment targets, except for the `flush` below. But by and far, users could use `<print>` on older deployment targets with no issues.[/-][+][libc++] Make <print> work without deployment target requirement[/+][libc++][print] Enables it on Apple backdeployment.
[libc++][print] Enables it on Apple backdeployment. (#76293)
[libc++][print] Enables it on Apple backdeployment. (llvm#76293)
[libc++][print] Enables it on Apple backdeployment. (#76293)