commit | 12917af8a2240174b87b63cd5c60174d18db2e24 | [log] [tgz] |
---|---|---|
author | Brian Silverman <bsilver8192@users.noreply.github.com> | Thu May 12 10:02:14 2022 -0700 |
committer | GitHub <noreply@github.com> | Thu May 12 10:02:14 2022 -0700 |
tree | 95ed0cee2caa363c2a084c6bda709fce0e6417f0 | |
parent | 1ea2472f7a73f14da4dfa98b393ddb252332ae91 [diff] |
Update Rust docs page (#7296) I think these changes reflect the current state, but I found it hard to track the state of some of the planned work. Hence why it'd be good to have it documented :) I also expanded some sections that I found misleading, as somebody familiar with Rust and FlatBuffers separately. Parts of these pages seem to be aimed at people familiar with FlatBuffers (ie via the other documentation pages) but not each language, which I'm trying to preserve. However, Rust does some things differently, and as somebody with expectations about how typical Rust APIs work the discussion of threading made me wonder what was different.
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.
Go to our landing page to browse our documentation.
and more in progress...
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.