Google Git
Sign in
pigweed/third_party/github/google/riegeli/b82c5bd99c51850d3e3b1628ab8211e0356f92a7
commit
b82c5bd99c51850d3e3b1628ab8211e0356f92a7
[log]
author
Marcin Kowalczyk <qrczak@google.com>
Mon Sep 15 09:37:40 2025 +0200
committer
qrczak <qrczak@google.com>
Mon Sep 15 09:39:51 2025 +0200
tree
7fb8bf94ef83f1efce19cc1d4509292ac049d192
parent
4689a84effdc64ed0f787a5f98a81bb4151ae164 [diff]
In `SerializeMessage` to `BackwardWriter`, use `CordWriter` instead of
`ChainWriter` for accumulating contents of message.

Protobuf has native support for `Cord`, which means that code working with
protobufs often have `Cord` or want `Cord`.

Cosmetics:

* Update a comment to mention `ScopedLimiterOrLimitingReader` instead of
  `LimitingReader`.

* Use CTAD.

PiperOrigin-RevId: 807119152
6 files changed
tree: 7fb8bf94ef83f1efce19cc1d4509292ac049d192
  1. doc/
  2. python/
  3. riegeli/
  4. tf_dependency/
  5. .bazelrc
  6. configure
  7. CONTRIBUTING.md
  8. LICENSE
  9. MANIFEST.in
  10. MODULE.bazel
  11. README.md
README.md

Riegeli

Riegeli/records is a file format for storing a sequence of string records, typically serialized protocol buffers. It supports dense compression, fast decoding, seeking, detection and optional skipping of data corruption, filtering of proto message fields for even faster decoding, and parallel encoding.

See documentation.

Status

Riegeli file format will only change in a backward compatible way (i.e. future readers will understand current files, but current readers might not understand files using future features).

Riegeli C++ API might change in incompatible ways.