We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is there any specific reason why NanoTimestamp and NanoInterval are not implemented as case classes and if not, would there be anything preventing it?
I noticed it when writing some protocols for serialization, I had to do custom protocols for these two when serializing TraceInfo and Segment.
The text was updated successfully, but these errors were encountered:
@ivantopo ping!!!
Sorry, something went wrong.
@elm- I see your point. I think is a really easy change and the users that want serialize TraceInfo and SegmentInfo will avoid a headache. ;)
770cb36
= core: NanoTimestamp and NanoInterval as case classes and closes #376
cf140b1
No branches or pull requests
Is there any specific reason why NanoTimestamp and NanoInterval are not implemented as case classes and if not, would there be anything preventing it?
I noticed it when writing some protocols for serialization, I had to do custom protocols for these two when serializing TraceInfo and Segment.
The text was updated successfully, but these errors were encountered: