In the field handler protocol, distinguish `Handle` functions for dynamic field numbers by naming them with the `DynamicHandle` prefix. This makes the interpretation of the signature of the given handling funtion unambiguous. While in practice the functions are called only when the role has been determined by `kFieldNumber` and by the presence of `Accept` functions, it is cleaner when the signature can be interpreted on its own: which parameter is `accepted` if it exists, which parameter is `repr`, and which parameters are `context...`. PiperOrigin-RevId: 842793312
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.