Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
N
nanopb
Manage
Activity
Members
Plan
Wiki
Code
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Terraform modules
Analyze
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
CodeLinaro
le
nanopb
Commits
6a0df689
Commit
6a0df689
authored
6 years ago
by
Pei Wang
Browse files
Options
Downloads
Patches
Plain Diff
Clarify the usage of callback fields inside oneof sections in the docs
parent
9a90d689
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/concepts.rst
+5
-0
5 additions, 0 deletions
docs/concepts.rst
with
5 additions
and
0 deletions
docs/concepts.rst
+
5
−
0
View file @
6a0df689
...
...
@@ -317,6 +317,11 @@ The user is expected to set the filed manually using the correct field tag::
Notice that neither ``which_payload`` field nor the unused fileds in ``payload``
will consume any space in the resulting encoded message.
When a C union is used to represent a ``oneof`` section, the union cannot have
callback fields or nested callback fields. Otherwise, the decoding process may
fail. If callbacks must be used inside a ``oneof`` section, the generator
option *no_unions* should be set to *true* for that section.
.. _`oneof`: https://developers.google.com/protocol-buffers/docs/reference/proto2-spec#oneof_and_oneof_field
Extension fields
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment