Skip to content

Adjust phrasing using "optional" when "singular" is meant #288

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.

Sign up for GitHub

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Adjust phrasing using "optional" when "singular" is meant #288

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions content/programming-guides/field_presence.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,11 +56,11 @@ deserializing wire-formatted messages:
- Duplicate `repeated` fields are typically appended to the field's API
representation. (Note that serializing a *packed* repeated field
produces only one, length-delimited value in the tag stream.)
- Duplicate `optional` field values follow the rule that "the last one
- Duplicate singular field values follow the rule that "the last one
wins."
- `oneof` fields expose the API-level invariant that only one field is set at
a time. However, the wire format may include multiple (tag, value) pairs
which notionally belong to the `oneof`. Similar to `optional` fields, the
which notionally belong to the `oneof`. Similar to singular fields, the
generated API follows the "last one wins" rule.
- Out-of-range values are not returned for enum fields in generated proto2
APIs. However, out-of-range values may be stored as *unknown fields* in the
Expand Down