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
Does capnproto-java have support for checking equality and generating hash's on StructReader's? My application is currently using Protobuf, and I am currently investigating capnproto as a replacement. Protobuf generates equals and hash methods on its generated objects, and my application relies on those methods.
Is it possible for the compiler to generate equals and hash methods for its objects, as well as handling schema changes like how Protobuf handles it? Requiring the programmer to write the methods and remembering to update the equals and hash methods when the schema changes is bound to create problems.
Thanks.
The text was updated successfully, but these errors were encountered:
I am working on a converter which needs to convert protocol buffer messages into cap'n'proto messages in both directions. In order to write integration tests I would like to have a convenient way of checking the converted messages after doing a back and forth conversion. As of now this is not possible as of the missing equals and hash methods.
Implementing them or doing a manual in depth comparison would be very time consuming and unmaintainable over time.
For testing purposes I would also go with an approach which does a textual comparison (JSON or capnp text format).
Does capnproto-java have support for checking equality and generating hash's on StructReader's? My application is currently using Protobuf, and I am currently investigating capnproto as a replacement. Protobuf generates equals and hash methods on its generated objects, and my application relies on those methods.
Is it possible for the compiler to generate equals and hash methods for its objects, as well as handling schema changes like how Protobuf handles it? Requiring the programmer to write the methods and remembering to update the equals and hash methods when the schema changes is bound to create problems.
Thanks.
The text was updated successfully, but these errors were encountered: