zeekay 263f3f2157 A list whose element has no width is readable too ...

The runtime could read a list of records — object(i, stride) — and a list of
pointers, but not the third shape: entries laid down as a four-byte length
followed by that many bytes, which is the only shape an element with no width
of its own can have. The Go and Rust runtimes have read it since they had
lists; here a generated accessor for it named a method that was not there.

bytes_at walks the entries and object_at reads one as the message it is. The
walk is what the shape costs — locating element i passes the ones before it —
and it is the reason a record list carries a stride instead.

2026-09-06 12:20:14 -07:00

..

rpc.hpp

The C++ SDK this repo has been describing

2026-09-05 14:46:04 -07:00

transport.hpp

The C++ SDK this repo has been describing

2026-09-05 14:46:04 -07:00

zap.hpp

A list whose element has no width is readable too

2026-09-06 12:20:14 -07:00