| commit | 1653db1903ef4484be22550afa12829899e3b7db | [log] [tgz] |
|---|---|---|
| author | Marcin Kowalczyk <qrczak@google.com> | Fri Sep 05 19:57:04 2025 +0200 |
| committer | qrczak <qrczak@google.com> | Fri Sep 05 19:57:48 2025 +0200 |
| tree | 40e64953f56571743edcf00906071655409bd680 | |
| parent | 40749dd63a71d6b3241dac5ebbb43f88098f0802 [diff] |
Optimize `ParseMessageWithLength()` and indirectly
`ParseLengthPrefixedMessage()` when `src` is statically known to be a
`LimitingReaderBase`.
In this case `ScopedLimiter` on `src` is used instead of creating a new
`LimitingReader`.
Add `ScopedLimiterOrLimitingReader` to capture this pattern.
This benefits `SerializedMessage{Reader,Rewriter}::OnParsedMessage()`.
PiperOrigin-RevId: 803526222
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.
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.