[
https://issues.apache.org/jira/browse/MESOS-2487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359606#comment-14359606
]
Zameer Manji commented on MESOS-2487:
-------------------------------------
I suggested two possible solutions in https://reviews.apache.org/r/31905/:
1. Create a custom protobuf compiler
[plugin|https://developers.google.com/protocol-buffers/docs/reference/cpp/google.protobuf.compiler.plugin]
that auto generates the implementations.
2. Use the protobuf C++ [reflection
api|https://developers.google.com/protocol-buffers/docs/reference/cpp/google.protobuf.message#Reflection]
for equality.
> Ensure protobuf "==" operator does not go out of sync with new protobuf fields
> ------------------------------------------------------------------------------
>
> Key: MESOS-2487
> URL: https://issues.apache.org/jira/browse/MESOS-2487
> Project: Mesos
> Issue Type: Task
> Reporter: Vinod Kone
>
> Currently when a new field is added to a protobuf that has a custom "=="
> operator defined, we don't make sure that the field is accounted for in the
> comparison. Ideally we should catch such errors at build time or 'make check'
> time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
