addressing @mdw-octoml's points: - I will add a comment addressing the semantics of the dtype field in the proto. - I will further refine the spec to avoid Any. I originally included google.protobuf.Any to capture the current tuple argument semantics, which seemingly supports arbitrary nesting here https://github.com/apache/incubator-tvm/blob/master/python/tvm/autotvm/task/task.py#L43-L63. It looks like stakeholders prefer to improve the format rather than use it as a snapshot, so this will warrant further discussion. - re: tightening up the proto semantics. I will add comments to the proto to elucidate the following: `version` refers to log format schema version as a SemVer string. An example of `tvm_version` is "0.7.dev1" and afaik that doesn't follow SemVer, but I will comment on the expected format. I agree that timestamp should be an ISO-8601 formatted timestamp and will make this change. - It looks like Config will have some drastic changes, so I will convert the Config message to containing a oneof field.
--- [Visit Topic](https://discuss.tvm.ai/t/rfc-canonicalizing-autotvm-log-format/7038/21) to respond. You are receiving this because you enabled mailing list mode. To unsubscribe from these emails, [click here](https://discuss.tvm.ai/email/unsubscribe/ff94f38a6467f771b166a646801e2fcaa67baed3c25b66b5ac02bbade110e009).
