Skip to content
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

Default value of a message conflicts with the proto spec #333

Open
clarkdonald opened this issue Aug 13, 2016 · 1 comment
Open

Default value of a message conflicts with the proto spec #333

clarkdonald opened this issue Aug 13, 2016 · 1 comment

Comments

@clarkdonald
Copy link

Hi,

In the ruby implementation, I've noticed that the default value of a message type is nil whereas in other languages the default value of a message type is the default instance. Other data types adhere to the proto spec - for example, the default value of a string field is an empty string rather than nil.

I've been burned by this conflicting behavior, and was wondering if this is the intended behavior for the ruby implementation?

@abrandoned
Copy link
Contributor

Probably not intended behavior.... We will do some looking at the c and Java implementations and get the compat mode in line

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants