On Wed, 23 Oct 2024 at 12:01, Jonathan Wakely via SG15
<sg15_at_[hidden]> wrote:
> My use case for constexpr_print is for "interactive" development during compile-edit-debug cycles. You add some prints, but then take them out again once you've understood how the code is compiling. So IMHO it really doesn't matter how that output is displayed. It could even go to a separate file.

Thanks, there's the answer to my pondering how the compiler could
control the output of a constexpr_print.

c++ -fconstexpr-print-output-file=-
c++ -fconstexpr-print-output-file=myprintzlog.txt