And the advantage of this is, it can be whatever you need it to be. Always the same value, new value under certain conditions, consistent without ODR, your build requirements drive that.
Not a limited implantation of whatever it is you decide right now that the compiler must do.

________________________________
From: Std-Proposals <std-proposals-bounces_at_[hidden]> on behalf of Thiago Macieira via Std-Proposals <std-proposals_at_[hidden]>
Sent: Friday, March 7, 2025 5:07:58 PM
To: std-proposals_at_[hidden] <std-proposals_at_[hidden]>
Cc: Thiago Macieira <thiago_at_[hidden]>
Subject: Re: [std-proposals] constexpr support for std::chrono::system_clock

On Thursday, 6 March 2025 23:03:16 Pacific Standard Time Tiago Freire via Std-
Proposals wrote:
> The simplest solution would be to just create a shell script that generates
> a file with the current time, let the build system call that shell script
> before build, and then not touch the compiler.

The drawback of that it that this does not obey $SOURCE_DATE_EPOCH (unless you
knew about it and coded your script that way), which in turn makes your code
non-reproducible. That adds to the workload of Linux distributions when trying
to figure out where the non-reproducibility came from.

That means there is an advantage of centralising this in the compiler.

--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
  Principal Engineer - Intel DCAI Platform & System Engineering
--
Std-Proposals mailing list
Std-Proposals_at_[hidden]
https://lists.isocpp.org/mailman/listinfo.cgi/std-proposals