Read other people's log files from various times in history.
Is your feature request related to a problem?
Not knowing which version of dart was used to produce some output.
Not knowing if the user has local modifications, committed or otherwise.
Describe your preferred solution
Not sure.
Include a version string at compile time "git describe --tags" that gets printed in the log file message
--------------------------------------
Starting ... at YYYY MM DD HH MM SS =
1884 4 16 10 29 13
Program Filter v0.0.1-13-ge74ab9573
--------------------------------------
Describe any alternatives you have considered
🔮 Any method of divination that can tell you the state of the code when it was compiled, store that in the executable, and output the info to the log file. I think git may be the way to go for what version of the code was committed at compile time (maybe also modified but not committed info - set a flag plus_unknown_mods).
Use case
Read other people's log files from various times in history.
Is your feature request related to a problem?
Not knowing which version of dart was used to produce some output. Not knowing if the user has local modifications, committed or otherwise.
Describe your preferred solution
Not sure. Include a version string at compile time "git describe --tags" that gets printed in the log file message
Describe any alternatives you have considered
🔮 Any method of divination that can tell you the state of the code when it was compiled, store that in the executable, and output the info to the log file. I think git may be the way to go for what version of the code was committed at compile time (maybe also modified but not committed info - set a flag
plus_unknown_mods).