| commit | 7cb0bcb21245418ea17e01a9ecdadb45d8d71dec | [log] [tgz] |
|---|---|---|
| author | Justin Davis <jtdavis777@gmail.com> | Sun Dec 21 17:36:47 2025 -0500 |
| committer | GitHub <noreply@github.com> | Sun Dec 21 17:36:47 2025 -0500 |
| tree | d8b746ce1d8c068a627770527487515bcc59badf | |
| parent | b1e7868db68aba89b2879c7e42b449fb80e2e0a9 [diff] |
C++ Feature: Mutable union getters (#8852) * generate mutable union accessors * add test * Revert "add test" This reverts commit 45e352b18f93c9d59afef6498f9948b2dcb8c0a4. * update file * formatter got in the way * merge conflicts * updated genned code * manually fix code gen bc I can't figure out why this file won't code gen --------- Co-authored-by: Wouter van Oortmerssen <aardappel@gmail.com>
FlatBuffers is a cross platform serialization library architected for maximum memory efficiency. It allows you to directly access serialized data without parsing/unpacking it first, while still having great forwards/backwards compatibility.
Build the compiler for flatbuffers (flatc)
Use cmake to create the build files for your platform and then perform the compilation (Linux example).
cmake -G "Unix Makefiles" make -j
Define your flatbuffer schema (.fbs)
Write the schema to define the data you want to serialize. See monster.fbs for an example.
Generate code for your language(s)
Use the flatc compiler to take your schema and generate language-specific code:
./flatc --cpp --rust monster.fbs
Which generates monster_generated.h and monster_generated.rs files.
Serialize data
Use the generated code, as well as the FlatBufferBuilder to construct your serialized buffer. (C++ example)
Transmit/store/save Buffer
Use your serialized buffer however you want. Send it to someone, save it for later, etc...
Read the data
Use the generated accessors to read the data from the serialized buffer.
It doesn't need to be the same language/schema version, FlatBuffers ensures the data is readable across languages and schema versions. See the Rust example reading the data written by C++.
Go to our landing page to browse our documentation.
Code generation and runtime libraries for many popular languages.
FlatBuffers does not follow traditional SemVer versioning (see rationale) but rather uses a format of the date of the release.
flatbuffers tag for any questions regarding FlatBuffers.To contribute to this project, see CONTRIBUTING.
Please see our Security Policy for reporting vulnerabilities.
Flatbuffers is licensed under the Apache License, Version 2.0. See LICENSE for the full license text.