-
Notifications
You must be signed in to change notification settings - Fork 811
New issue
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
Known Issue: unknown behaviour for proto.Equal #13
Comments
This should be reported in another issue, but you could check out in test/thetest.proto
The equal method does the following
Does this help? |
I've run into problems with This is the proto: And the error is:
It's because of this special handling of Any ideas for a work-around? |
You are welcome to contribute a fix with a test, but an easier fix might be to just generate equal methods.
|
Thanks! The equal extension looks good! But I've run into another issue with it, reported in #283. |
When using a customtype that is an array proto.Equal does not work, outputs log message The Line 151 in 5628607
reflect.Array case which explains why this does not work.
Before digging into the code I also tried defining |
From awalterschulze on May 07, 2014 21:17:58
proto.Equal(a, b Message) bool has not been tested with all gogoprotobuf scenarios.
If you are using this please comment so I can up the priority.
Original issue: http://code.google.com/p/gogoprotobuf/issues/detail?id=13
The text was updated successfully, but these errors were encountered: