Closed
Description
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 theflush
below. 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_unicode
and others, since they would basically have no deployment target requirements anymore.
Originally posted by @ldionne in #73262 (comment)