diff options
| author | Juan Cruz Viotti <jv@jviotti.com> | 2021-01-21 16:23:54 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-01-21 12:23:54 -0800 |
| commit | 52e2177069750c05adeb24f76c3a9d538c5d33b7 (patch) | |
| tree | 3e82a56e0361c16e016338563178705acb34e828 | |
| parent | 760c657551230c0c29d4c9a43fbf62602fe4b5a8 (diff) | |
| download | flatbuffers-52e2177069750c05adeb24f76c3a9d538c5d33b7.tar.gz flatbuffers-52e2177069750c05adeb24f76c3a9d538c5d33b7.tar.bz2 flatbuffers-52e2177069750c05adeb24f76c3a9d538c5d33b7.zip | |
Remove invalid claim that Protocol Buffers does not support unions (#6413)
Protocol Buffers v3 supports the `oneof` operator:
https://developers.google.com/protocol-buffers/docs/proto3#oneof
Signed-off-by: Juan Cruz Viotti <jv@jviotti.com>
| -rw-r--r-- | docs/source/FlatBuffers.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/source/FlatBuffers.md b/docs/source/FlatBuffers.md index 2a2133f7..bbd2cb0f 100644 --- a/docs/source/FlatBuffers.md +++ b/docs/source/FlatBuffers.md @@ -64,8 +64,8 @@ Protocol Buffers is indeed relatively similar to FlatBuffers, with the primary difference being that FlatBuffers does not need a parsing/ unpacking step to a secondary representation before you can access data, often coupled with per-object memory allocation. The code -is an order of magnitude bigger, too. Protocol Buffers has neither optional -text import/export nor schema language features like unions. +is an order of magnitude bigger, too. Protocol Buffers has no optional +text import/export. ### But all the cool kids use JSON! |