barrister icon indicating copy to clipboard operation
barrister copied to clipboard

Is the timestamp really needed in the parsed IDL?

Open colega opened this issue 6 years ago • 2 comments

Having the timestamp in the parsed IDL (and a similar one in the autogenerated Go code) makes it impossible to generate same binaries twice from the same code.

It also adds unnecessary complexity of merging if two people have regenerated the code from IDLs in the same repository.

Is there any benefit of having that timestamp included in the parsed IDL?

colega avatar Dec 22 '17 15:12 colega

It can be useful for tracing build issues, but I would be fine with adding a switch to the barrister CLI that would omit it from the generated JSON

coopernurse avatar Dec 28 '17 23:12 coopernurse

Added a flag in #13, after this it would be interesting to skip them in the generated Go code too, what do you think?

colega avatar Jan 24 '18 12:01 colega