You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use build timestamp to distinguish different version of application binary is a common way in other languages.
eg: C has macros "__DATE__" and "__TIME__" to fetch compiler time.
But golang has no way to achive this feature nowadays.
I have made a patch to provide fllow API to achive it.
It will be my pleasure that if go team can accept this feature in go repository. The branch
The text was updated successfully, but these errors were encountered:
vipally
changed the title
runtime/time: API runtime.BuildTimestamp required to report appication build time
runtime/time: API runtime.BuildTimestamp required to report application build time
Dec 19, 2017
odeke-em
changed the title
runtime/time: API runtime.BuildTimestamp required to report application build time
proposal: runtime, time: add API BuildTimestamp to report an application's build time
Dec 19, 2017
If you want this, use the linker's -X option. We are not going to do this by default, as producing bit-identical binaries for bit-identical inputs is a goal. It would also prevent caching of go build results for main packages. Closing.
Uh oh!
There was an error while loading. Please reload this page.
Use build timestamp to distinguish different version of application binary is a common way in other languages.
eg: C has macros "__DATE__" and "__TIME__" to fetch compiler time.
But golang has no way to achive this feature nowadays.
I have made a patch to provide fllow API to achive it.
runtime.BuildTimestamp defines a buildtimestamp value which will be written by linker(cmd/link).
time.BuildTime() converts runtime.BuildTimestamp() to time.Time.
The expected usage of BuildTimestamp API is as follow:
It will be my pleasure that if go team can accept this feature in go repository.
The branch
The text was updated successfully, but these errors were encountered: