Open zw963 opened 1 week ago
This issue has been mentioned on Crystal Forum. There might be relevant details there:
https://forum.crystal-lang.org/t/print-compile-time-when-app-starts/6278/16
I don't see a reasonable use case for embedding the build time. It can be considered an antipattern because it hinders reproducible builds. If you really want do this, you can use the run macro. But I don't think there's a good reason to encourage this via a macro API.
Users have their own purposes for use Time.local
in the compile time, this is a so basic function, don't expect to seek help from date
crystal run
or crystal eval
.
Feature Request
Check discuss on this
Following is a example code
The output like this:
Above time serve as a
build time
,deploy time
, orrelease date
for CLI app, is used for confirm we are packaged the binary or deployed the website which built on specified time.I consider we should get the
Time.local
use a better way than awfulcrystal eval ...
workaround.