Rename functions returning distances between buffer pointers:
* `buffer_size()` → `start_to_limit()`
* `{written_to,read_from}_buffer()` -> `start_to_cursor()`

This avoids a naming conflict with a `buffer_size()` setting in various
`Options`, avoids a weird case when only one buffer-related name differs between
`Reader` and `Writer`, and is more explicit.

`available()` stays unchanged. It is fundamental when reading/writing directly
at `cursor()` so it can have a shorter name.

PiperOrigin-RevId: 406318134
60 files changed
tree: 5e2680e15f8d162afe4efb8cf63f134e2f2b99a6
  1. doc/
  2. python/
  3. riegeli/
  4. tf_dependency/
  5. third_party/
  6. .bazelrc
  7. configure
  8. CONTRIBUTING.md
  9. LICENSE
  10. MANIFEST.in
  11. README.md
  12. WORKSPACE
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.